The commits were in fact against 5.2.5-SNAPSHOT (just check the pom files in trunk for revision 1051293) so the close version in jira was indeed correct.
This probably occured when 5.2.x was moved to where it is now and trunk was "upgraded" for 5.3 On Wed, Mar 30, 2011 at 21:11, Igor Drobiazko <[email protected]> wrote: > Yes, we don't do them very often. They also have a small number of issues, > so that it's easy to review them. But in case of major releases like 5.3.0 > (probably with more than 100 issues), I would go crazy, if I would check > every single issue for the release version. So, an assigned committer should > take care for providing a proper fix version. > > On Wed, Mar 30, 2011 at 7:29 PM, Howard Lewis Ship <[email protected]> wrote: > >> Both were done by Dan Adams, I believe. Obviously, something is wrong >> with our "process" for such things to slip through ... though we don't >> do maintenance releases that often. >> >> On Wed, Mar 30, 2011 at 10:22 AM, Igor Drobiazko >> <[email protected]> wrote: >> > Also this one is only fixed for 5.3.0: >> > >> > https://issues.apache.org/jira/browse/TAP5-1378 >> > >> > On Wed, Mar 30, 2011 at 7:20 PM, Howard Lewis Ship <[email protected]> >> wrote: >> > >> >> It might apply to other things marked as "fixed" as well. >> >> >> >> On Wed, Mar 30, 2011 at 10:17 AM, Igor Drobiazko >> >> <[email protected]> wrote: >> >> > Damn, I didn't check it. I just relied on the committers to set the >> >> "fixed >> >> > version" field correctly. >> >> > >> >> > On Wed, Mar 30, 2011 at 6:46 PM, Howard Lewis Ship <[email protected]> >> >> wrote: >> >> > >> >> >> https://issues.apache.org/jira/browse/TAP5-742 >> >> >> >> >> >> I think there's an error in the bug and the release notes; this >> >> >> appears to NOT be fixed in 5.2.5, just in trunk (5.3.0). I can find >> >> >> no trace of the code there --- am I missing something?. We should >> >> >> double check the release notes where this is listed as fixed. >> >> >> >> >> >> -- >> >> >> 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: [email protected] >> >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> >> >> >> > >> >> > >> >> > -- >> >> > Best regards, >> >> > >> >> > Igor Drobiazko >> >> > http://tapestry5.de >> >> > >> >> >> >> >> >> >> >> -- >> >> 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: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> > >> > >> > -- >> > Best regards, >> > >> > Igor Drobiazko >> > http://tapestry5.de >> > >> >> >> >> -- >> 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: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > Best regards, > > Igor Drobiazko > http://tapestry5.de > -- Andreas Andreou - [email protected] - http://blog.andyhot.gr Apache Tapestry PMC / http://chesstu.be owner Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
