Subject: Re: [boost] [1.65.0] Point release?
From: Seth (bugs_at_[hidden])
Date: 2017-08-26 11:40:29
On 26-08-17 13:30, Daniel James via Boost wrote:
> git checkout boost-1.65.0 -b fixes/1.65
> git cherry-pick (commit-hash)
Going the cherry-pick route is asking for trouble IME.
By cherry-picking instead of basing of an existing (permanent)
reference/commit you run the risk of introducing regressions when the
next release uses the same change, but from different commit.
It also becomes hard to have clear release notes (the release notes for
the point release are essentially separate from either the base or the
next release. This is not what end-users expect.)
Just my $0.02.
Then again, this model might be PERFECT for true hot-fixes. Just be sure
to communicate what a point release is, and what it is used for. Make
syre maintainers AND end-users are aware of the purpose.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk