You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by Justin Mason <jm...@jmason.org> on 2007/06/18 18:12:13 UTC

Re: [Bug 5419] kill -HUP `pidof spamd` causes the ps name to change from "spamd" to "perl"

Daryl C. W. O'Shea writes:
> Theo Van Dinter wrote:
> > On Mon, Jun 18, 2007 at 11:26:43AM -0400, Daryl C. W. O'Shea wrote:
> >>>>   Target Milestone|3.2.2                       |3.2.3
> >>> Are we in a hurry to get 3.2.2 out?
> >> As I mentioned in bug 5510, I want to put an end to the problems 
> >> installing via CPAN really soon since there's been a lot of noise about 
> >> it.  I'm OK with waiting another week though.
> > 
> > I'd rather have a little bit of time between releases which fix more
> > than one bug. :)
> 
> Ideally I would too.  The problem is, though, most CPAN users won't know 
> how to install it without doing a "force install".
> 
> As of now it looks like, pending some reviews, we'll have at least 8 
> bugs fixed for 3.2.2.
> 
> I'm not dead set for a release though, I had just thought that I had 
> some support for one now based on my comment of "I think we need to fix 
> this and cut a release soon.  If we aim for Wednesday it leaves the 
> weekend for anyone who feels like playing whack-a-bug." and jm's 
> response of "I think I may have a fix nearly ready...".  Perhaps that 
> wasn't in response to my comment.

Yeah, I'm afraid it wasn't ;)   I was kind of +0 at that stage
to the idea of a release, so I just left it uncommented-on, and dealt
with the bit I wanted to comment about...

> > We also want to make sure to stay on top of releases though, otherwise we'll
> > end up with the 3.1.8/3.1.9 type of thing.
> 
> Yeah, no kidding.  I had given up hope of getting bugs reviewed for 3.1 
> before I forgot what they were fixing sometime during the winter.

yep, that sucked. ;)

I think I'd be keen to wait about a week... the danger, as Theo noted, is
that we get over-eager to fix the CPAN bug and push out a release quickly,
then *another* serious 3.2.2 bug appears, requiring a fast 3.2.3 in turn!
(This is all standard practice in the early part of every release cycle,
in my experience, btw.)

Maybe if we build a tarball on Friday?  (by we I mean "not I", though,
I've seen enough tarballs last week and have a nursery to paint ;)

--j.