On Fri, Aug 29, 2008 at 12:44 AM, Craig L Russell <[EMAIL PROTECTED]> wrote:
Thanks for checking these.
> There should be a KEYS file high up in your directory structure. I didn't
> look too hard for it elsewhere, but just downloaded your key from the public
> keyserv. I later found a KEYS in the
Hi Aidan,
First, the good news:
The process is spot on. Summary of votes, location of artifacts to
vote on. The only thing I'd like to see in the process is the nominal
close date for this vote.
I found the release artifacts and downloaded one of them to take a
look: qpid-incubating-M3.t
There were a few SNAFUs with headers and LICENSE in the last release,
so I've rolled RC3 for and would like to restart the vote to release
Apache Qpid M3.
I started the vote on qpid-dev at 2008-08-22:
http://markmail.org/message/2a6pmx3sdgvh5bu5
And closed it on 2008-08-27 http://markmail.org/mess
On Wed, Aug 27, 2008 at 5:49 PM, Aidan Skinner <[EMAIL PROTECTED]> wrote:
> It is with a building sense of anticipation that I am able to inform
> you that Qpid has voted to release Apache Qpid M3.
>
> I started the vote on 2008-08-22: http://markmail.org/message/2a6pmx3sdgvh5bu5
> And closed it o
On Wednesday 27 August 2008 5:22:22 pm Carl Trieloff wrote:
> they are located in the sub-dir for each language, and are specific for
> each lang. someone who installs C++
> does not care about Python or Java readme etc or visa versa.
That is all irrelevant for the qpid-incubating-M3.tar.gz packag
On Wed, 2008-08-27 at 18:14 +0100, Aidan Skinner wrote:
> On Tue, Aug 26, 2008 at 7:03 PM, Craig L Russell <[EMAIL PROTECTED]> wrote:
>
> > Do you have any ideas on how to make sure that people read and understand
> > the documentation, either the existing or proposed update?
>
> I suspect it's a
