Boost logo

Boost :

Subject: Re: [boost] [1.45.0] Permission to merge trunk to release for (Polygon)
From: Simonson, Lucanus J (lucanus.j.simonson_at_[hidden])
Date: 2010-11-11 11:59:07

Eric Niebler wrote:
> On 11/11/2010 8:13 AM, Fernando Cacciola wrote:
>> Hi,
>> As reported by Eric Niebler, the release brunch did not had the swap
>> member that existed in the trunk for a long time.
>> I just merged it locally and run the tests on the release branch.
>> Can I commit the changes?
> No, we're only taking showstopper bug fixes (and documentation tweaks)
> at this point. But the changes to optional will be gladly welcomed
> once
> 1.45 is out the door.
>> P.S: The test suite changed as well due to the different swap.
>> P.S.2: I've also been reported on a couple of minor documentation
>> issues, so I've fixed this on both the trunk and the release branch.
> Fine.
>> P.S.3: Going over all the differences I've found a trivial change in
>> the testsuite for value_initialized: The trunk version uses the
>> lightweight "minimal" test tools instead of the full test tools.
>> I've merged this one as well.
> This is an oops. Please don't merge anything to release bug
> showstopper bug fixes and doc tweaks.

Oops. I merged some bug fixes yesterday and noticed I forgot to add a header and merged that today to fix compilation failures that showed up in release regressions.

The schedule said 1.45 was supposed to be released on the 1st, but I forgot that we pushed it out for show stopper bug fixes. The particular bugs fixed revolve around polygon resizing for general polygons being almost completely broken in the 1.44 release.

We have the option of reverting my changes to the release branch or keeping them if release regressions pass. I would prefer to get the issues with resizing fixed in 1.45 since they have already been reported by users of the 1.44 release.


Boost list run by bdawes at, gregod at, cpdaniel at, john at