Andy, don't get me wrong. I don't feel good with releasing 5.2 with a bug. Not at all. But I feel even worse when I think about the date of the last stable release: April 23, 2009. We hadn't a release for over 18 months. Sometimes, you just need to get things done. So, I could live with this small bug and provide a further bug fix release 1 week later.
We should change our release strategy and should be more agile. We need a release aver 2-3 months. On Wed, Dec 15, 2010 at 4:21 PM, AndyB <[email protected]> wrote: > > > Well I didn't raise the issue as a blocker, and I know it's easy to > override > and fix this issue. I'm not concerned so much for my project, I am fixing > this for our end of sprint release right now. > > What I am concerned with, however, is Tapestry's quality and reputation. A > final release with a subtle environment triggered problem like this in it, > when it was found before the release? Really? You're good with that? I'm > surprised quite honestly with that attitude from Tapestry team, and not for > the first time either. > > I know the vote is over, but we only just found the issue having had our > migration to 5.2.4 delayed by the behaviour changes in > Link.getAbsoluteURI(). I considered it important enough to spend the time > to > report immediately for the good of the Tapestry project, even though I have > a load of other stuff I should be doing. That's why I post after the end of > the vote, once I realised that Howard hasn't done the release and newspost > yet. > > > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/VOTE-Tapestry-5-2-4-as-Stable-Release-tp3300722p3306462.html > Sent from the Tapestry - Dev mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Best regards, Igor Drobiazko http://tapestry5.de
