Why not push out 5.0.15 as a non-beta capital-R Release, Howard goes on vacation, the accumulated smaller bugs get fixed or nailed down over the next month, Howard comes back and releases an also non-beta 5.0.16, and then heads off down the 5.1 path.
That way Tapestry 5 is out of beta (holy crap!), Howard can enjoy his vacation, and we know a few quick fixes are going to show up in six weeks or so. Ned Jackson Lovely +1 (so non-binding as to be ludicrous) On 9/16/08, Filip S. Adamsen <[EMAIL PROTECTED]> wrote: > Hi, > > On 2008-09-16 20:08, Ulrich Stärk wrote: >>> c) Abort 5.0.15 (again!), fix these, start again. >> >> I'd only do this if any of these issues are real blockers for any reason. > > You don't think TAPESTRY-2674 is a real blocker? Imagine if this was a > problem with the German localization... Just saying. > > Like I said, *I* can handle this being in 5.0.15, but others might not > be able to. Also, since da (Danish) is a supported locale by default, > this might even hit non-Danish apps if tapestry.supported-locales is not > overridden to exclude it. > > In the end, it's up to Howard and the rest of the committers. > > -Filip > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- njl --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
