Hi,
In Papyrus, we don’t switch branches until the
final release (Which is RC4 for us). Any new feature is postponed
(e.g. pending on Gerrit) until the release is complete. This is
mainly to avoid reconfiguring the build & scripts due to
switching branches.
We’re however experimenting a new approach this
year: we’ve created a new branch after Feature Freeze (M7), for the
next release. This is a temporary branch, that will be rebased to
master after the final release (RC4). Once the branch is rebased,
the current master will be renamed to maintenance, and the rebased
branch will become the new master
The point with this approach is to be able to push
new features on a dedicated branch, where we can have complete
builds/validation, and we can merge several features on the same
branch to identify conflicts early, without changing the current
structure for the master branch (Same branch name, same build
configuration...)
We don’t have too many contributions on this new
branch, so it’s hard to tell whether it was useful at all. In
general, at this time, we should be focusing on bug fixes anyway;
not on features for the next yearly release. So, I’d say, new
branches can wait :) but it really depends on your plans and
contributions
Regards,
Camille
De :
papyrus-rt-dev-bounces@xxxxxxxxxxx
[mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx] De la part
de Ernesto Posse
Envoyé : mardi 17 mai 2016 02:32
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : [papyrus-rt-dev] Feature freeze and git
repo