No, we have moved to a versioning scheme where odd numbers are development 
versions and even numbers will be release version. 

So 0.6 is the latest release, 0.7 is the current development stream, and 0.8 
will be the next release (with development then ongoing as 0.9).

Robbie

> -----Original Message-----
> From: Tim Chen [mailto:[email protected]]
> Sent: 26 October 2010 19:14
> To: [email protected]
> Subject: Re: Qpid releases
> 
> Just a side question about qpid releases,
> 
> Is 0.7 already released?
> 
> From http://qpid.apache.org/download.cgi, it looks like the latest is
> still 0.6.
> 
> Thanks,
> 
> Tim
> 
> ----- Original Message -----
> From: "Robbie Gemmell" <[email protected]>
> To: [email protected]
> Sent: Tuesday, October 26, 2010 10:38:31 AM GMT -08:00 US/Canada
> Pacific
> Subject: Re: Qpid releases
> 
> Hi Justin, welcome to non-lurker status :)
> 
> The current state of the release is that trunk entered feature freeze
> yesterday with intent that we will spend this week and next
> concentrating on bug fixing before branching for the 0.8 release
> candidate process (and thus any further bug fixing required) and
> reopening trunk for any 0.9 development underway.
> 
> I prepared an alpha build on Friday (available at
> http://people.apache.org/~robbie/qpid/0.7alpha1 ) to allow initial
> identification of packaging issues etc, from which I have noticed a
> couple and will correct them. I also ran Apache RAT across the build
> and supplied the output for review, such that we might fix any
> licencing issues preventing release. The output shows that there are a
> number of unlicensed files in the tree, many of which we must update
> and many many more which we should update; ideally there would be few
> if any unlicenced files so that whenever we do introduce new ones it
> isnt necessary to go looking for them in the 400 files we currently
> have identified. This is something I have asked everyone to help with
> and would appreciate any assistance with.
> 
> A further task required is to update JIRAs currently targeted for 0.7,
> checking their status is accurate and if they haven't been or won't be
> worked on for 0.8 then tagging them as Affects 0.7/0.8 and then moving
> them out to unknown Fix For. I had hoped to make a dent in this today
> but wont be making it to that until later this week now. Again this
> applies to everyone so all help would be appreciated, particularly for
> the C++ and .Net components I am less familiar with.
> 
> Although JIRA itself will provide the overall release notes, pulling
> together some features of note for the announcement email is also
> something which will need done.
> 
> I prepared an initial wiki page this morning for use in these tasks,
> to allow viewing and/or recording information relating to the release.
> It is available at:
> https://cwiki.apache.org/confluence/display/qpid/0.8+Release
> 
> Regards,
> Robbie
> 
> On 26 October 2010 16:05, Justin Ross <[email protected]> wrote:
> > Hi, everyone. I'd like to introduce myself and ask some questions
> about Qpid
> > releases.
> >
> > I've been lurking on qpid-dev and submitting the odd patch for Qpid
> for
> > some time. As part of my work, I develop and maintain a continuous
> test
> > and build system for Qpid.
> >
> > Starting next month, my work focus is changing. It will be my job to
> > help streamline our release process. In particular, for Qpid, this
> means
> > I will have time to devote to Qpid releases.
> >
> > So, I want to help, and I have some ideas. These have already been
> > discussed at least a little in the past. I intend to provide the time
> > and resources to get us started.
> >
> > I'm focused on these:
> >
> >   - Helping Robbie with 0.8. What is its current status? Are there
> >     release tasks that I can take on?
> >
> >   - Produce regular, time-based releases starting with 0.10.
> >
> >   - Improve the release infrastructure to support "push button"
> >     releases.
> >
> > Thanks,
> > Justin
> >
> >
> > ---------------------------------------------------------------------
> > Apache Qpid - AMQP Messaging Implementation
> > Project:      http://qpid.apache.org
> > Use/Interact: mailto:[email protected]
> >
> >
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]
> 
> 
> ---------------------------------------------------------------------
> Apache Qpid - AMQP Messaging Implementation
> Project:      http://qpid.apache.org
> Use/Interact: mailto:[email protected]



---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:[email protected]

Reply via email to