Most incubator projects stick with milestone releases (Mx) until they graduate. As Alan pointed out incubator projects are not considered matured (not necessarily the code, but the community) and endorsed by the ASF. That's the reason why we have to add the following disclaimer to our releases. https://svn.apache.org/repos/asf/incubator/qpid/trunk/qpid/DISCLAIMER
So as Alan points out we should reserve the 1.0 for our first release after graduation. A lot of the incubator projects make a lot of PR around the 1.0 release after graduation. So we should definitely make use of that opportunity and stick with M4 for the next release. I believe we are ready as community and could push for graduation soon, so lets be patient with our versioning until then :). Regards, Rajith. On Wed, Oct 8, 2008 at 8:48 AM, Alan Conway <[EMAIL PROTECTED]> wrote: > On Tue, 2008-10-07 at 20:39 +0100, Robert Greig wrote: > > 2008/10/7 Aidan Skinner <[EMAIL PROTECTED]>: > > > > > The C++ requirements seem to be quite restrictive. Linux Kernel/APR > style > > > would be my preference, kicking us to 0.4.0 for everything from 0.3 / > M3. > > > > Do we want to have the major version as zero? That implies to me that > > qpid is immature, which I would argue is not the case. The codebase > > has been evolving over the space of several years now and there are > > many production deployments of several components (e.g. I personally > > know about significant usage of the java broker and client). > > > > So I would suggest 1.4.0. > > > > RG > > As an Apache project we are not "mature" or "released" until we > graduate. I'd be inclined to go with 0.4 and reserve 1.x for our first > graduated release. If we go with 1.4 then our graduated releases will > have to start at 2.0. > > > > -- Regards, Rajith Attapattu Red Hat http://rajith.2rlabs.com/
