You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by Alan Conway <ac...@redhat.com> on 2007/04/19 21:14:34 UTC
C++ release plan.
I'm a fool. Somehow I "volunteered" to C++ M2 release. Gordon/Andrew
I'd like your input, and anyone else who has any to offer. I'll put
together a release plan (list of JIRAs) on Monday.
In my view the release criteria for C++ is a usable package of
everything we did in 0-8, nothing more. I don't anticipate any
significant coding:
So the things we need to consider are:
- Showstopper bugs for using 0-8.
- Non-showstoppers that are still a problem on trunk, now may be a good
time to clean house.
- Doc/demo improvements that will also still be relevant on trunk, again
now is may be a good time to clean up our act.
- Interop tests with the other projects.
- Release notes describing what AMQP features are/are not implemented,
known bugs etc.
NB: that was a list of things to *consider* not things to *do*. I'll
make a list of things to do on Monday in the form of a set of JIRAs with
some rough prioritization. Any and all input will be cheerfully
incorporated or ignored at my whim.
Cheers,
Alan.
Re: C++ release plan.
Posted by Alan Conway <ac...@redhat.com>.
On Mon, 2007-04-23 at 20:26 +0100, Marnie McCormack wrote:
> Alan,
>
> Thanks - that's really great ! Not foolish, brave :-)
Its often hard to tell the difference.
Cheers,
Alan.
Re: C++ release plan.
Posted by Marnie McCormack <ma...@googlemail.com>.
Alan,
Thanks - that's really great ! Not foolish, brave :-)
Bfn,
Marnie
On 4/19/07, Rajith Attapattu <ra...@gmail.com> wrote:
>
> Alan,
>
> Once u guys agree on the plan, please update the following page with the
> details.
> http://cwiki.apache.org/qpid/m2-release.html
>
> Regards,
>
> Rajith
>
> On 4/19/07, Alan Conway <ac...@redhat.com> wrote:
> >
> > I'm a fool. Somehow I "volunteered" to C++ M2 release. Gordon/Andrew
> > I'd like your input, and anyone else who has any to offer. I'll put
> > together a release plan (list of JIRAs) on Monday.
> >
> > In my view the release criteria for C++ is a usable package of
> > everything we did in 0-8, nothing more. I don't anticipate any
> > significant coding:
> >
> > So the things we need to consider are:
> >
> > - Showstopper bugs for using 0-8.
> >
> > - Non-showstoppers that are still a problem on trunk, now may be a good
> > time to clean house.
> >
> > - Doc/demo improvements that will also still be relevant on trunk, again
> > now is may be a good time to clean up our act.
> >
> > - Interop tests with the other projects.
> >
> > - Release notes describing what AMQP features are/are not implemented,
> > known bugs etc.
> >
> > NB: that was a list of things to *consider* not things to *do*. I'll
> > make a list of things to do on Monday in the form of a set of JIRAs with
> > some rough prioritization. Any and all input will be cheerfully
> > incorporated or ignored at my whim.
> >
> > Cheers,
> > Alan.
> >
> >
> >
>
Re: C++ release plan.
Posted by Rajith Attapattu <ra...@gmail.com>.
Alan,
Once u guys agree on the plan, please update the following page with the
details.
http://cwiki.apache.org/qpid/m2-release.html
Regards,
Rajith
On 4/19/07, Alan Conway <ac...@redhat.com> wrote:
>
> I'm a fool. Somehow I "volunteered" to C++ M2 release. Gordon/Andrew
> I'd like your input, and anyone else who has any to offer. I'll put
> together a release plan (list of JIRAs) on Monday.
>
> In my view the release criteria for C++ is a usable package of
> everything we did in 0-8, nothing more. I don't anticipate any
> significant coding:
>
> So the things we need to consider are:
>
> - Showstopper bugs for using 0-8.
>
> - Non-showstoppers that are still a problem on trunk, now may be a good
> time to clean house.
>
> - Doc/demo improvements that will also still be relevant on trunk, again
> now is may be a good time to clean up our act.
>
> - Interop tests with the other projects.
>
> - Release notes describing what AMQP features are/are not implemented,
> known bugs etc.
>
> NB: that was a list of things to *consider* not things to *do*. I'll
> make a list of things to do on Monday in the form of a set of JIRAs with
> some rough prioritization. Any and all input will be cheerfully
> incorporated or ignored at my whim.
>
> Cheers,
> Alan.
>
>
>