On Mon, May 7, 2012 at 12:47 AM, Craig Small <csmall-procps@xxxxxxxxxx> wrote: > On Thu, May 03, 2012 at 08:28:13PM +0200, Sami Kerola wrote: >> Timing of these patches are a bit problematic as the project is >> nearing to next release, so though decision whether to include fixes >> or stand known problems in release. To make matters worse while >> sorting out globing I noticed a bug, which can be fixed with following >> patch. Notice that all of the sysctl patches are in my git to ease up >> maintainer job. > > We'll put the three that are in your mike branch in. That should be it. OK. You probably noticed I pushed few additional bug fixes more to mike branch, and I leave it to you whether to take or leave. > Always seems we find bugs just before closing things off. Bugs happen, so it's the question how do we handle them. Perhaps making one rc (Release Candidate), or few in bad case, could ease up bug hunt before final release. For the v3.3.3 we're already late to do that. The second thing I can think of is to clean up bug queue. I would find it intuitive that before release there is nothing open in http://bugs.debian.org/cgi-bin/pkgreport.cgi?pkg=procps;dist=unstable Could be reasonable to get the v3.3.3 out, and soon after (in two-three weeks) v3.3.4 which is about dealing every single bug out we can find? -- Sami Kerola http://www.iki.fi/kerolasa/