Changes in the development Git branches
8 views
Skip to first unread message
Andrei Tsaregorodtsev
Aug 19, 2015, 12:09:45 PM8/19/15
to diracgrid-develop
Hi,
In order to be more flexible with the tests of the new releases I suggest that a new release branch is created
as soon as a new prerelease series is started. This will allow to start testing a set of new features destinated
to the next release while the previous release is not yet certified. This will need attention of the developers
making Github Pull Requests when choosing the target branch. If a new feature is chosen to go into the next release,
let say vXrY, the PR should be made against the rel-vXrY branch rather than against the integration branch.
In particular, the release v6r14 is out and we start preparing the new v6r15 release. The rel-v6r15 branch is
created. The current PRs aginst the integration branch will be incorporated in this rel-v6r15 branch, but future
PRs should be done with a properly chosen destination branch.
Any comments are welcome.
Cheers,
Andrei
In order to be more flexible with the tests of the new releases I suggest that a new release branch is created
as soon as a new prerelease series is started. This will allow to start testing a set of new features destinated
to the next release while the previous release is not yet certified. This will need attention of the developers
making Github Pull Requests when choosing the target branch. If a new feature is chosen to go into the next release,
let say vXrY, the PR should be made against the rel-vXrY branch rather than against the integration branch.
In particular, the release v6r14 is out and we start preparing the new v6r15 release. The rel-v6r15 branch is
created. The current PRs aginst the integration branch will be incorporated in this rel-v6r15 branch, but future
PRs should be done with a properly chosen destination branch.
Any comments are welcome.
Cheers,
Andrei
Christophe HAEN
Aug 20, 2015, 7:02:51 AM8/20/15
to diracgrid-develop
I strongly support this
Cheers,
Chris
Philippe Charpentier
Aug 20, 2015, 8:23:47 AM8/20/15
to diracgrid-develop
Yes!
I also think we should be more agile with minor releases: 3 to 4 months is far too long a waiting time for new features that are very useful and ready...
Le mercredi 19 août 2015 18:09:45 UTC+2, Andrei Tsaregorodtsev a écrit :
Reply all
Reply to author
Forward
0 new messages