I've been promoting the idea of following the Apache ethic a bit more closely; release the code but then wait for a while before voting on its stability. That's the plan I'd like to pursue for T5, that we may start calling something a release candidate, then retroactively vote it as the stable release.
On Jan 22, 2008 7:54 AM, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > If possible, I'd like to release 4.1.4 at the end of this month > (little bit over a week). More specifically - the client I'm working > with would like to move to a stable release before their product hits > the QA team. > > Just checking to be sure that's ok with everyone. Doesn't mean > people can't go crazy with 4.1.4 changes from now til then. > > -- > Jesse Kuhnert > Tapestry / OGNL / Dojo team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Creator Apache Tapestry and Apache HiveMind --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
