Boost logo

Boost :

From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2019-11-23 00:28:54


I think we can cherry-pick these seven commits from develop into master
as post-beta merges:

| * cc311eb8e - Mention C++11 in meta/libraries.json (4 days ago)
<Mateusz Łoskot>
| * c24e8b251 - Add release notes in Markdown format (#404) [ci skip]
(11 days ago) <Mateusz Łoskot>
| * 60e579b84 - Typo in README [ci skip] (12 days ago) <Mateusz Łoskot>
| * 9f5f24aff - Add Markdown linting with Node package markdownlint
[ci skip] (3 weeks ago) <Mateusz Łoskot>
| * cb5b2e0ec - doc/ clarify steps building docs [ci skip]
(3 weeks ago) <Mateusz Łoskot>
| * e2c26ce2c - Remove logo as unnecessary [ci skip]
(3 weeks ago) <Mateusz Łoskot>
| * 19eed887e - Fix FreeNode link and hash escape [ci skip]
(3 weeks ago) <Mateusz Łoskot>

They qualify as the Policy's "Documentation fixes and other minor
changes not affecting code",
so they do not require the Boost release manager's permission.

Once those seven commits are in master, the develop branch will differ
by just one commit:

| * 84b155630 - Remove include/boost/gil/version.hpp file as unused
(#403) (13 days ago) <Mateusz Łoskot>

which we can not cherry-pick as such deprecation is potentially
"breaking changes"
and, according to the policy, should wait until the next release.

Shall we merge those seven commits into the master?


---------- Forwarded message ---------
From: Michael Caisse via Boost <boost_at_[hidden]>
Date: Thu, 21 Nov 2019 at 17:37
Subject: [boost] [release] 1.72.0 post-beta merges
To: <boost_at_[hidden]>
Cc: Michael Caisse <mcaisse-lists_at_[hidden]>

The master branch is is now open for post-beta merges, but only as
described in the Post-Beta Merge Policy.

See <>

Unsubscribe & other changes:

Mateusz Loskot,

Boost list run by Boost-Gil-Owners