On Sat, Jul 21, 2012 at 20:55:27 +0200, Jonas Smedegaard wrote: > Is the noise of the non-crucial changes so problematic (a.k.a. > unpleasing) that the release team considers the current package > unsuitable for getting an exception from the freeze? > > I honestly did not consider that "noise" as "significant changes not > related to the bug to be fixed", as it is phrased at the fine > http://release.debian.org/wheezy/freeze_policy.html. > > > Do the release team consider the package unsuitable for freeze exception > due to the lack of bug reference in the changelog (the bug was > unfortunately unavailable to reference at the time the package was > produced and I honestly was unaware that such reference was problematic > for the release team to get passed in the freeze exception bugreport)? > > Do the release team consider the package unsuitable for freeze exception > due to the user-only oriented changelog entry - i.e. lack of verbose > enough details in changelog for release managers to follow _how_ the > issue was fixed? > > Would it be more helpful of me to upload another package release that > rephrased the changelog to be more helpful for release managers to > understand how non-newest-debhelper-style packaging was performed > internally? Should I do that in addition to the user-oriented changelog > entry or instead of it? > > Would it be more helpful if I had not asked these questions but instead > just uploaded a new package fixing these three issues raised by Cyril? > So I think I'll answer these all at once because I think they boil down to the same thing. For a request like this, if it takes more than 5 minutes to process it's a waste of our time. Having a clear changelog helps avoid that, as does not arguing or getting on your high horse when asked clarification questions. And by helping that, it helps get your request approved, which I guess is what you want? Cheers, Julien
Attachment:
signature.asc
Description: Digital signature