Re: Master branch is now open for bug fixes

From: Marshall Clow (mclow.lists_at_[hidden])
Date: 2022-11-17 16:45:49

On Nov 17, 2022, at 6:28 AM, Stefan Seefeld via Boost <boost_at_[hidden]> wrote:
> 
> I'd like to ask for permission to merge the boost.python's `devel` branch
> to `master`. There are a few minor bugfixes accumulated over recent months,
> all tested and stable, but I unfortunately missed the previous window to
> merge those into master.

Do they all fit into the categories listed below?  (https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy <https://github.com/boostorg/wiki/wiki/Releases:-Beta-Merge-Policy>)

        • Showstoppers. Criteria: Bugs or other problems so serious that the release is seriously compromised if not fixed. Procedure: After discussion on the developers list, release managers will specify how the problem is to be attacked, and what effect it will have on schedule.

        • Code changes and fixes. Procedure: Ask release managers for permission. Libraries with regressions showing in trunk testing should not be merged into the release branch. If it is discovered that this has occurred, then the merge should be reverted. Rationale: While we do want to fix problems, particularly regressions, stability is a major concern at this point in the release cycle.

        • Documentation fixes and other minor changes not affecting code. Criteria: Changes not requiring regression testing and unlikely to impact other libraries. Procedure: Merges to branches/release are OK, after fix applied to trunk, and do not require a release manager's permission. Important: If applicable, check the daily snapshot to verify the change did not break the documentation build.

— Marshall

> 
> Thanks,
> 
> On Thu, Nov 17, 2022 at 9:23 AM Marshall Clow via Boost <
> boost_at_[hidden]> wrote:
> 
>> The master branch is now open for bug fixes and documentation changes.
>> Other changes by release manager permission, as described in
>> 
>> https://github.com/boostorg/wiki/wiki/Releases%3A-Beta-Merge-Policy
>> 
>> The next deadline: On December 7th, master closes for all changes.
>> 
>> As always, the calendar is at https://www.boost.org/development/ <
>> https://www.boost.org/development/>
>> 
>> — Marshall
>> 
>> 
>> _______________________________________________
>> Unsubscribe & other changes:
>> http://lists.boost.org/mailman/listinfo.cgi/boost
>> 
> 
> 
> -- 
> 
>      ...ich hab' noch einen Koffer in Berlin...
> 
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost