[
https://issues.apache.org/jira/browse/FINERACT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205049#comment-17205049
]
Michael Vorburger commented on FINERACT-1154:
---------------------------------------------
> the branch deleted then after the release has been tagged.
That works as well for me, and is probably actually much clearer than what I
had originally (above) in mind. Seeing people comment that they "will be
sending a PR to the 1.4 branch" e.g. in FINERACT-1165 further reinforces that
it would be best to simplify this, to avoid confusion.
> So to action this, I suppose we should just ensure that there's a tag for
> each past release, and then delete all the release branches - right?
Sounds like a plan to me! Do you want to go ahead and do that? Feel free to
"grab" the issue and assign it to yourself and action it... up to you if you
also want to post to the dev list about when it's done.
[~aleks] we'll assume that silence here means "no objections" from you! ;)
> Git branch strategy is wrong, use tags instead
> ----------------------------------------------
>
> Key: FINERACT-1154
> URL: https://issues.apache.org/jira/browse/FINERACT-1154
> Project: Apache Fineract
> Issue Type: Bug
> Reporter: Michael Vorburger
> Assignee: Michael Vorburger
> Priority: Major
> Fix For: 1.5.0
>
>
> It seems wrong to me that we have 20 open branches (on
> https://github.com/apache/fineract/branches), including for the just released
> 1.4.0. IMHO a 1.4.0 should be a tag not a branch, and there could be a branch
> named 1.4.x instead - if anyone actually wanted to maintain that (which I
> doubt anyone does).
> [~aleks], [~ptuomola] or anyone else reading along here, do you agree?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
