Release status?

[Duncan Findlay <du...@debian.org>]

Sorry I haven't had much time recently to do much coding for SA. I'm
in the middle of exams and I'm hoping to get some more time soon...

Anyways, what's the current status of the 3.0 release? I think our
(last?) release schedules suggested we would be doing mass-checks
around this time.

There are currently 49 open bugs depended on by the 3.0.0 tracker (bug
3208) and about 288 bugs with a milestone of 3.0.0.

We really need to go through and fix remaining bugs and postpone those
that aren't started. I'd really like to see 3.0.0 release in
May. Perhaps we should add a 3.0.1 milestone for bugzilla? Theo, would
you like to propose a new release schedule?

Would it be useful to schedule a bug squashing party at some point? 
The next week or so is bad for me, but others might be able to get
stuff done.

-- 
Duncan Findlay

Re: Release status?

[Theo Van Dinter <fe...@kluge.net>]

On Sun, Apr 18, 2004 at 04:44:39PM -0400, Theo Van Dinter wrote:
> If I don't hear from anyone by the 20th, I'll assume we can move forward.

Since I haven't heard anything, we'll move forward. :)

I set the default milestone to 3.1.0.  I'll post a proposal schedule
later today.

-- 
Randomly Generated Tagline:
"I would rather spend 10 hours reading someone else's source code than
 10 minutes listening to Musak waiting for technical support which isn't."
 (By Dr. Greg Wettstein, Roger Maris Cancer Center)

Re: Release status?

[Theo Van Dinter <fe...@kluge.net>]

On Tue, Apr 13, 2004 at 03:01:05PM -0400, Theo Van Dinter wrote:
> I haven't had a chance to ask -- are we all happy with the bugs in the
> tracker?  Quinlan put up a list of the open tickets in 3.0, I modified
> it to be my proposed list of what to fix/punt, Justin added some more,
> and then after a week or two the tracker came into existence.

Anyone?  At all?  I'm happy with the current list of things to do (there's
more than enough).  I'd like to shift the default queue to 3.1 and start
moving tickets over (again).  We can then plan a bug squashing event,
and come up with a general release schedule again.

If I don't hear from anyone by the 20th, I'll assume we can move forward.

-- 
Randomly Generated Tagline:
All Scottish food is based on a dare.

Re: Release status?

[Michael Parker <pa...@pobox.com>]

On Tue, Apr 13, 2004 at 03:01:05PM -0400, Theo Van Dinter wrote:
> On Tue, Apr 13, 2004 at 01:14:38PM -0400, Duncan Findlay wrote:
> 
> > Would it be useful to schedule a bug squashing party at some point? 
> > The next week or so is bad for me, but others might be able to get
> > stuff done.
> 
> That gets back to the bug list again.  I think the stuff that's currently
> in there is non-trivial, so ...  :(
> 

I propose at least one bug squash event to whittle down the number of
bugs before we even think about a schedule.  That will hopefully help
identify what really needs to be fixed/added to 3.0.0 before release.
It will also help eliminate all of the trivial/works for me bugs that
are in Bugzilla at the moment.

Michael

Re: Release status?

[Theo Van Dinter <fe...@kluge.net>]

On Tue, Apr 13, 2004 at 01:14:38PM -0400, Duncan Findlay wrote:
> Anyways, what's the current status of the 3.0 release? I think our
> (last?) release schedules suggested we would be doing mass-checks
> around this time.

It's about the same as it was a month ago, unfortunately.  The release
schedule I proposed did actually pass vote-wise, but we decided not to
implement it at that point due to "issues".

> There are currently 49 open bugs depended on by the 3.0.0 tracker (bug
> 3208) and about 288 bugs with a milestone of 3.0.0.

I haven't had a chance to ask -- are we all happy with the bugs in the
tracker?  Quinlan put up a list of the open tickets in 3.0, I modified
it to be my proposed list of what to fix/punt, Justin added some more,
and then after a week or two the tracker came into existence.

> We really need to go through and fix remaining bugs and postpone those
> that aren't started. I'd really like to see 3.0.0 release in

yep.

> May. Perhaps we should add a 3.0.1 milestone for bugzilla? Theo, would

I don't think May is viable at this point.  Assume 3 weeks for mass-check
and score generation, and IMO, a minimum of 2 weeks for testing.  The end
of May is 6 weeks from now, so we'd have 1 week to finish off all the
open bugs, which I don't think is going to happen.

> you like to propose a new release schedule?

Well, it depends on the current bug list.  If we all think it's good
(I haven't really looked at it, fwiw,) then we should come up with
estimates to get the list done, and go from there.

> Would it be useful to schedule a bug squashing party at some point? 
> The next week or so is bad for me, but others might be able to get
> stuff done.

That gets back to the bug list again.  I think the stuff that's currently
in there is non-trivial, so ...  :(

-- 
Randomly Generated Tagline:
"When you're having a bad day and it seems like people are trying your
 patience to no end, remember, it takes 42 muscles to frown and only 4 to pull
 the trigger on a decent sniper rifle." - Erik Fichtner