[jbosstools-issues] [JBoss JIRA] (JBIDE-24789) Find a way to avoid freeze of master for several days

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-24789?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13443385#comment-13443385 ] 

Nick Boldt commented on JBIDE-24789:
------------------------------------

You're asking for the exact process we've used for the last year, which we decided was unnecessary overhead. You can't got 3 days without committing to master? Each sprint is 21 days -- this gives you 18 days for commits and 3 days for accumulation of PRs, writing doc/N&N, and preparing for the forthcoming sprint.

> 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)