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

Michael Adam obnox at samba.org
Mon Jun 18 15:04:23 MDT 2012


Jeremy Allison wrote:
> On Mon, Jun 18, 2012 at 08:21:39PM +0200, Karolin Seeger wrote:
> > 
> > > We should add that we add the known bugs to the release notes,
> > > that might be also very useful for admins.
> > 
> > I don't think that this is neccessary, because
> > a) nobody is reading release notes and
> > b) that is what bugzilla is for.
> > I have no idea how long the release notes will be if I have to add each
> > existing bug. But if all of you agree, I will have to.
> 
> No, that would be insane. I hope that's not what
> people are suggesting. We have far too many reported
> bugs (note I'm not saying actual, we get far more
> reported than are actually real).

Well, the idea was to add a snapshot of the list of
known bugs at the point of the relase.
As a service for admins and packagers
so they can easily tell what the known issues were at
the time of the release.

If it is too much effort to create this list or
if the list would take too much room, then we can
skip this.

The more imprtant point is the scheduled bugfix releases and
the inability to block a release by a "severe" bug.

Cheers - 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/53a25c48/attachment.pgp>


More information about the samba-technical mailing list