comanage-dev - [comanage-dev] Proposed New Hotfix Branch Strategy
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To: comanage-dev <>
- Subject: [comanage-dev] Proposed New Hotfix Branch Strategy
- Date: Wed, 25 May 2016 15:28:48 +0200
I'm leaning towards suggesting that we always have a pending hotfix
release. eg: We're working on 1.1.0, but until it's released we have
1.0.5 pending. If we decide to release 1.0.5, then we have 1.0.6 pending
(and so on...). All bugfixes always go into hotfix, then merge into
develop as usual.
When 1.1.0 is ready, we simultaneously release the last 1.0.x (say 1.0.6
in this example), which will be the last of the 1.0 series. We then
start on 1.2.0, and meanwhile start the same hotfix pattern, but now for
1.1.1, 1.1.2, etc.
Does that make sense? Thoughts?
(I'm going to create 1.0.5 in JIRA anyway, as bugfixes are starting to
pile up and we will likely want one more maintenance release before 1.1.0.)
Thanks,
-Benn-
- [comanage-dev] Proposed New Hotfix Branch Strategy, Benn Oshrin, 05/25/2016
- Re: [comanage-dev] Proposed New Hotfix Branch Strategy, Arlen Johnson, 05/25/2016
- Re: [comanage-dev] Proposed New Hotfix Branch Strategy, Scott Koranda, 05/27/2016
Archive powered by MHonArc 2.6.16.