And if anyone is desperate to start work on new features, we can always cut a development branch for 1.2 work.
On 6/23/05, Knut Wannheden <[EMAIL PROTECTED]> wrote: > On 6/22/05, Howard Lewis Ship <[EMAIL PROTECTED]> wrote: > > The hardest part is knowing when to stop. I'm very pleased with > > HiveMind 1.1; it has co-evolved with Tapestry 4.0 and is quite capable > > ... but contains only a fraction of the things it could. Still it > > would be good to stop. AH has come on, and will help with > > documentation and bug fixing, but I think its even more important to > > pick a release date and stick with it, deferring everything else to > > HiveMind 1.2. And I'd like to see an even shorter cycle for 1.2. > > > > How about Labor Day -- Sep 5th? > > > > Sounds good. That should give us enough time to do some bugfixing, > improving the documentation and releasing an RC before Labor Day. > > --knut > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
