Why not create a release prep branch for each release when ready? The
"gitflow" treatment of master is that's what's currently "in production" or
whatever. I don't really care for that model, but it is popular. For
libraries that support multiple versions, I don't know how realistic that
is.
On We
Given that the 'master' branch is normally where development takes
place, this problem is going to keep recurring.
Maybe MATH should consider using 'master' as the normal development
branch and 'release' or somesuch for the release candidate.
On 29 May 2016 at 22:42, Gilles wrote:
> Hi.
>
> Tha
Hi.
Thanks for willing to participate, but the "master" branch should be
modified only by merging the "develop" into it (before preparing a
release).
Cf. rationale in "doc/development/development.howto.txt" (in the
"develop" branch).
Regards,
Gilles
On Sun, 29 May 2016 21:28:11 + (UTC), db
