Release Maintenance (WAS Re: Goals for 2.22)

Max Kanat-Alexander mkanat at
Sun Jul 10 02:24:13 UTC 2005

On Sat, 2005-07-09 at 22:01 -0400, Luis Villa wrote:
> Is the plan to maintain a given release for X number of years, or to
> maintain X number of total releases at any one time?

	Well, I seem to recall the plan being to support releases on a
basically time-based schedule, but that we'd be freezing on a time-based
schedule anyhow... so I'm pretty sure it's for X number of releases.

	I'm pretty sure that our support period was planned to be 1.5 years
(although that's probably too long), which would give us three branches
and a trunk, with only one branch getting actual bugfixes *most* of the
time, except during RC periods, where two branches would be getting
standard bugfixes.

	Looking at that now, I think that's probably not fully realistic for
the actual number of developers/reviewers that we have currently. :-)

	Perhaps a 12-month support period for a release would be better.
Consultants could pick up the slack on old releases, if they so desired.
People could probably start whole businesses around that, if they felt
like it.

Everything Solved: Experts at Bugzilla... and everything else, too.

More information about the developers mailing list