Re: [boost] [new Warningspolicy] MSC4180 ontheMaintenance Guidelines

Subject: Re: [boost] [new Warningspolicy] MSC4180 ontheMaintenance Guidelines
From: Stewart, Robert (Robert.Stewart_at_[hidden])
Date: 2009-11-24 08:20:22

Emil Dotchevski wrote:
> On Mon, Nov 23, 2009 at 10:28 AM, Stewart, Robert
> <Robert.Stewart_at_[hidden]> wrote:
> >>
> > It would be reasonable to state that if a developer changes
> > the trunk in such a way as to introduce warnings on an
> > inaccessible platform, that developer is required to seek
> > support from other developers to discover a mutually
> > compatible change.
>
> I'd call this common sense.

In many cases, common sense isn't so common.

> Assuming you're not proposing that we
> introduce some kind of bureaucracy or a committee to help manage
> warnings, and assuming everyone agrees that we don't want warnings in
> the build logs, then simply reporting a warning will get it removed.

Being clear about what's expected removes doubt, ambiguity, and confusion.

> Or are you envisioning a different process?

I'm envisioning only what I wrote above: a policy statement.

_____
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.