Subject: Re: [boost] [1.45] Beta 1 release candidates
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2010-11-08 07:17:30
John Maddock wrote:
> > We're still showing active showstoppers for 1.45
> > (https://svn.boost.org/trac/boost/report/29). If we ship
> > anyway, we need to have a discussion about what
> > "showstopper" means, and we need a policy for what to do
> > about them prior to release.
> They may well be addressable, but I note that most have only
> just been filed - maybe we need a cutoff date past which
> folks can't file showstoppers for the next release on the
> grounds that it's probably already too late?
No release or schedule is so important that a release should be pushed when there is an outstanding showstopper issue, period. Doing otherwise means to sacrifice the quality for which Boost has been and should be known. Reclassifying an issue may be appropriate, or an issue may have appeared after a release is pushed, but an empty showstoppers report should be a prerequisite for a release to be announced. Of course, a last minute issue could appear. In that case, assess its severity then reclassify it or query the list for consensus on how to proceed if there is no obvious recourse.
Eric's idea to push library owners to clear showstoppers is necessary, too.
Rob Stewart robert.stewart_at_[hidden]
Software Engineer, Core Software using std::disclaimer;
Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.