Blockers in Bugfix-Releases (Re: [Release Planning 3.6] Samba 3.6.6 on May 31 (was May 24)?)

[Michael Adam]

Stefan (metze) Metzmacher wrote:
> Am 18.06.2012 12:49, schrieb Michael Adam:
> > 
> > Proposal (again): time-based releases:
> > ======================================
> > 
> > I propose that we agree on a time-based schedule for bugfix
> > releases. E.g. a bugfix release every 4 or 6 weeks
> > (whatever works for you, maybe even 8 weeks) for the current
> > stable release branch. Then we have a list of bugs that we
> > would like to fix for that release (basically any bug open
> > against the major version). If at freezing time, at least
> > one bug is fixed, the list ist closed and the release is done
> > as scheduled no matter which other bugs are still open.
> > 
> > In this mode, the users will get _each_ bugfix in a relase
> > as soon as possible after it becomes available. And the users
> > are not deprived of important bugfixes because other bugfixes
> > are not available yet.
> > 
> > Handling security issues:
> > =========================
> > 
> > When a security issue is reported non-publically, and a
> > bugfix release is imminent, (within a couple of days, say),
> > we should do the bugfix release on schedule and release
> > the security release afterwards as soon as we have a fix.
> > 
> > If we have a fix for the security issue before the freezing
> > period for the bugfix release starts, we should release the
> > security fix before the scheduled release and see whether
> > the original date for the bugfix release can be kept or
> > needs to be deferred by some days.
> > 
> > If there is a bug report that is public but there is a suspicion
> > that it might be security relevant, I have not recipe yet. But I
> > am inclined to treat it as any other bug until there is proof.
> > 
> > 
> > Votes?
> > Opinions?
> 
> Sounds like a good plan!
> 
> We should add that we add the known bugs to the release notes,
> that might be also very useful for admins.

Oh, that is a very usefull addition, indeed! +1

Michael

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 206 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20120618/496e51bd/attachment.pgp>