What are the chances that I'll be able to merge a bug fix to the release branch? This one: http://svn.boost.org/trac/boost/ticket/2157 just came in, and I've already fixed it on trunk. Assuming that the next cycle of the trunk tests don't show anything amiss, would I be permitted to merge the fix? The bug will not cause crashes, but it will lead to incorrect results when matching the end-of-line assertion ($) against internal line breaks, which is fairly common usage scenario. I have high confidence in the fix. These are the relevant changesets: http://svn.boost.org/trac/boost/changeset/47899 http://svn.boost.org/trac/boost/changeset/47901 -- Eric Niebler BoostPro Computing http://www.boostpro.com
Eric Niebler wrote:
What are the chances that I'll be able to merge a bug fix to the release branch? This one: http://svn.boost.org/trac/boost/ticket/2157 just came in, and I've already fixed it on trunk. Assuming that the next cycle of the trunk tests don't show anything amiss, would I be permitted to merge the fix?
Yes, although it may not appear in the beta.
The bug will not cause crashes, but it will lead to incorrect results when matching the end-of-line assertion ($) against internal line breaks, which is fairly common usage scenario. I have high confidence in the fix.
These are the relevant changesets: http://svn.boost.org/trac/boost/changeset/47899 http://svn.boost.org/trac/boost/changeset/47901
--Beman
Beman Dawes wrote:
Eric Niebler wrote:
What are the chances that I'll be able to merge a bug fix to the release branch? This one: http://svn.boost.org/trac/boost/ticket/2157 just came in, and I've already fixed it on trunk. Assuming that the next cycle of the trunk tests don't show anything amiss, would I be permitted to merge the fix?
Yes, although it may not appear in the beta.
Thanks, the test results looked good this morning, so I went ahead and merged the change to release (changeset 47910). I'll be away this weekend, but I'll have my laptop with me and I'll try to check in on the release tests once or twice to make sure everything is copacetic. -- Eric Niebler BoostPro Computing http://www.boostpro.com
Eric Niebler wrote:
Beman Dawes wrote:
Eric Niebler wrote:
What are the chances that I'll be able to merge a bug fix to the release branch? This one: http://svn.boost.org/trac/boost/ticket/2157 just came in, and I've already fixed it on trunk. Assuming that the next cycle of the trunk tests don't show anything amiss, would I be permitted to merge the fix?
Yes, although it may not appear in the beta.
Thanks, the test results looked good this morning, so I went ahead and merged the change to release (changeset 47910). I'll be away this weekend, but I'll have my laptop with me and I'll try to check in on the release tests once or twice to make sure everything is copacetic.
No hurry. There will be a lull for several days while we wait for feedback from the beta. --Beman
participants (2)
-
Beman Dawes -
Eric Niebler