But doesn't stabilizing mean to fix at least the major bugs? Especially if patches are provided? Otherwise it looks more like hibernating.
Markus On Wed, Nov 18, 2009 at 10:30 AM, Howard Lewis Ship <hls...@gmail.com> wrote: > On Tue, Nov 17, 2009 at 11:56 AM, Kalle Korhonen > <kalle.o.korho...@gmail.com> wrote: >> On Tue, Nov 17, 2009 at 11:01 AM, David Rees <dree...@gmail.com> wrote: >>> On Tue, Nov 17, 2009 at 2:00 AM, Ciaran Wood <ciar...@gamesys.co.uk> wrote: >>>> The issue you were thinking of is >>>> https://issues.apache.org/jira/browse/TAP5-714 - there is a patch w/tests >>>> attached to the issue so a committer can probably fix this one! >>> >>> Thanks, voted. BTW, it affects all versions of IE that I tested. >>> It's a show-stopper, not a minor issue - should raise the priority, >>> especially since it has a patch. >> >> Agree, maybe not a showstopper, but not a minor either. >> >>> How can we encourage the developers to get a release out with some of >>> these issues? Are people building their own local version with >>> patches applied? >> >> Starting to veer off-topic, but I think the issue there is that Howard >> has traditionally done all the releases, but he hasn't been actively >> involved in bug fixing lately (and probably shouldn't need to be). >> Howard's also been complaining about some difficulties with releasing >> but I don't know the details. I know though that setting up a fully >> automated release process with Maven can sometimes be taxing but the >> efforts are well worth it. Especially for bug fix releases, >> confidently being able to roll up yet another point release is great >> (at times, I release my projects a few times a week since it's so >> simple). I fully agree with you that more frequent point releases for >> T5 are badly needed. > > Actually, my intent has been to let T5 stabilize with 5.1 for a bit. > In addition, as some of my postings have mentioned, I feel that if I > start coding 5.2 features and bug fixes, I'll be less likely to start > on a book. > > Doing releases is merely time consuming; Maven isn't an overwhelming > factor in that ... it's more about the constraints of getting releases > out, voted and mirrored that can take several days from start to > finish. However, Andreas has been working on a new approach based on > the Nexus tool for Maven ... we'll have to see what the new process > looks like. > > > >> >> I'd avoid building your own versions if at all possible. Not because >> building would be too difficult, but with local versions, you need to >> deal with everything else included - deploying, maintaining, >> distributing and keeping track of versions. Use nightly snapshots from >> Formos if you have to and lock down to specific unique snapshot >> whenever possible. >> >> Kalle >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org >> For additional commands, e-mail: users-h...@tapestry.apache.org >> >> > > > > -- > Howard M. Lewis Ship > > Creator of Apache Tapestry > > The source for Tapestry training, mentoring and support. Contact me to > learn how I can get you up and productive in Tapestry fast! > > (971) 678-5210 > http://howardlewisship.com > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
