On Wed, Nov 18, 2009 at 1:57 AM, Howard Lewis Ship <hls...@gmail.com> wrote: > On Wed, Nov 18, 2009 at 1:52 AM, Markus Joschko <markus.josc...@gmail.com> > wrote: >> But doesn't stabilizing mean to fix at least the major bugs? >> Especially if patches are provided? Otherwise it looks more like >> hibernating. > > True; the big question is whether bugs should be fixed for 5.1 (i.e., > leading up to a 5.1.0.6 release perhaps) or whether they can be > bundled into a 5.2 alpha release.
Most projects seem to do the following: Decide which "major" releases are currently supported. These releases get security patches and bugfixes. Any significant new features go into the next "major" release. So the question is: What versions of Tapestry is supported? Is 5.0.x supported? Is 5.1.0.x supported? If both are supported, they should both get any security and important bugfixes. And those security / bugfixes should go into trunk for the next major release as well. The biggest issue is manpower - since as you said, it takes a bit of work to backport patches and push out a release - but even if they only get into snapshot builds (a 5.0.19-SNAPSHOT and 5.1.0.6-SNAPSHOT) that are built nightly from the appropriate branch, that would satisfy the needs of a lot of users without having to push out an actual release too often. -Dave --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
