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

Karolin Seeger kseeger at
Fri Jun 22 12:20:57 MDT 2012

On Fri, Jun 22, 2012 at 07:56:40PM +0200, Christian PERRIER wrote:
> Quoting Karolin Seeger (kseeger at
> > > > 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.
> > > 
> > > At least, having the list of bugs fixed by a given release in the
> > > release notes would be helpful.
> > 
> > I don't get what is missing right now.
> > As I have already pointed out at this year's SambaXP, the release notes
> > contain all older release note of the branch. So you can track down which
> > bug was fixed in which release. Please clarify what should be added.
> My understanding was that this part of the discussion was about
> listing *all* bugs fixed in a said release (since the former one) or
> only some of them.

Currently, all fixed bugs are listed! Even minor ones (sometimes I do skip
minor doc fixes). 

The discussion was about listing known and unfixed bugs.
> What I find helpful is having such a list of all Bugzilla bugs fixed
> by X.Y.Z release sicne X.Y.Z-1. Only bug numbers is enough,
> indeed. And details could be given for those that are "important"
> enough (which is the biggest part of the work, I guess as one needs to
> cook up a summary for each).

Exists: Bug number + short description.
> If release notes *already* do that, then fine and I don't need
> anything more.
> And, yes, cumulative release notes are also very helpful
> (particularly, indeed, if they list all fixed bugs, including minor
> ones).
> Shortly said, I haven't checked if listing all fixed bugs between two
> releases is what you're doing right now, Karolin (I know you're doing
> cumulative RN) or if you "only" list those you find noticeable enough,
> that was the point.

I am listing all.



More information about the samba-technical mailing list