Subject: Re: [boost] [1.48.0] Status?
From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2011-11-08 11:04:38
On Nov 8, 2011, at 7:35 AM, Beman Dawes wrote:
> On Tue, Nov 8, 2011 at 9:55 AM, Marshall Clow <mclow.lists_at_[hidden]> wrote:
>> On Nov 8, 2011, at 6:06 AM, Beman Dawes wrote:
>>> Are there any 1.48.0 showstoppers outstanding? We are scheduled to
>>> release right now.
>> Well, there are 72 open tickets in Trac marked as "showstopper". :-
> From the standpoint of shipping a release, at the end of a release
> cycle, about the only thing I consider a showstopper is something that
> makes most of Boost unusable, particularly for a popular platform. I
> also get concerned when a library, particularly a popular one, has a
> lot of failures.
> IFAIK, none of those tickets come anywhere close to that level of
> concern. I'm guessing most were classified as "showstopper" because
> they were important to the submitter.
You'll get no argument from me on that score.
However, I think we ought to go through those bugs and decide which, if any, actually are "showstoppers"
[ Before the next (1.49) release, I mean ]
In https://svn.boost.org/trac/boost/wiki/TicketWorkflow, we have (in fact, I think I wrote):
Severity - how bad is this ticket?
Showstopper - this problem is so bad, that we should hold up a release if it's not fixed. Note that the release managers and/or the library maintainers may have different opinions.
Regression - something used to work (in a previous release), but no longer does.
Problem - the default value.
Optimization - this makes the library work better (usually with a patch enclosed).
Cosmetic - minor problems, like using the wrong "they're/there/their" in a comment, or a typo in the documentation. Do not be discouraged from creating tickets for "minor" issues like this. They're easy to fix, and they make boost better.
Then again, I think that the status of the bug list, and getting things fixed, needs some serious work anyway.
(given that we currently have almost 1250 open tickets)