[
https://issues.apache.org/jira/browse/FINERACT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17202660#comment-17202660
]
Petri Tuomola commented on FINERACT-1154:
-----------------------------------------
[~vorburger] - fully agreed. Tags are immutable which makes them much better
for releases, as then you know you are looking at what has been released. And
if we are using a tag to mark the release then why do we need to keep the
branch as well?
But if we don't have the release branches (which is good), should we then have
a "master" branch on which the releases are tagged - i.e. in line with this:
[https://nvie.com/posts/a-successful-git-branching-model/] ? That's how I've
normally done it, but I'm sure there are other approaches as well...
> 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)
