[
https://issues.apache.org/jira/browse/FINERACT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203620#comment-17203620
]
Petri Tuomola commented on FINERACT-1154:
-----------------------------------------
Yes - it definitely makes sense that we would create a branch for every release
in preparation of the release - e.g. 1.4.0 or 1.4.x etc. But that should in my
view be done just in the "run-up" of the release and the branch deleted then
after the release has been tagged.
And I don't see a must-have requirement for a "master" branch - and if we
don't have one, we don't have to worry about what to call it...
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?
> 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)
