[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=13446577#comment-13446577 ] 

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

1. Creating branches can be done by script.
2. Updating parent pom can be done by script.
3. Updating jbosstools-* project root poms to use the new parent pom can be done by script, *except for projects with Protected Branches like fuse and fuse-extras*.

We've never created milestone branches for AM1, AM2, AM3. But we used to create a branch when code freezing for the 4th sprint to GA, so that as soon as GA bits were done and ready to build, devs could continue in master while the jobs were updated to use the 4.5.0.x branch.

For this train, we decided to NOT create the 4.5.0.x branch to simplify the amount of changes/steps involved in releases. 

> 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
>             Fix For: 4.5.x
>
>
> 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)