[
https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugi...
]
Aurélien Pupier commented on JBIDE-24789:
-----------------------------------------
personally, i try to avoid to work on weekend, so it is 12 days for commit and 3 days for
accumulation of PRs, writing doc/N&N and not preparing the forthcoming sprint as we
are in Kanban.
And for this release, it is not 3 days but a week, so 10 days of commit and 5 days of
accumulations.
So for each version of 4 sprints, it is 22 days of commit and 8 days of freeze, it means
more than 30% of the time frozen :(
it also means that we always need to check: are we frozen? are we not frozen? ; I already
merged a PR during previous freeze just because I forgot it was code freeze and realized
half a day later.
Find a way to avoid freeze of master for several days
-----------------------------------------------------
Key: JBIDE-24789
URL:
https://issues.jboss.org/browse/JBIDE-24789
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Affects Versions: 4.5.0.Final
Reporter: Aurélien Pupier
Currently, for each milestone, final release, the master branch is frozen for several
days which is decreasing productivity and increase risk at the end of code freeze (as
everybody wants to merge a lot of PRs at the same time)
it would be nice to find a way to avoid the freeze on the master branch.
Proposal:
- create a branch for each milestone/release:
-- it allows to continue working on master
-- it allows to provide blocker/critical fix if needed on the branch
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)