Typos; I meant a 1.1 final release, which should precede the Tapestry 4.0 final release.
The question is: what bugs ABSOLUTELY CAN'T WAIT FOR 1.1? I bet there are very few in that category, especially considering that we can start cranking on 1.1 almost immediatelly. We could branch and do it today. On 8/1/05, Achim Huegen <[EMAIL PROTECTED]> wrote: > I agree, though your version numbering is confusing me a little bit ;-) > Do you have certain bugs in mind? > I found 11 open bugs, that all have 'major' priority. > > Achim > > Howard Lewis Ship wrote: > > Things have slowed down a lot in HiveMind; I've been concentrating on > > Tapestry, and HiveMind 1.1 has everything Tapestry 4.0 needs for the > > moment. I have some great ideas for 1.1, but not the cycles > > (currently) to delve into that. > > > > Achim is on board and committing, which is great. I'd still like to > > get another 1.1 beta release out, perhaps after a round of bug fixing. > > In fact, what I'd prefer would be to get to a release candidate for > > 1.0 and then start concentrating on 1.1. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- 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]
