[
https://issues.apache.org/jira/browse/FINERACT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17203531#comment-17203531
]
Michael Vorburger commented on FINERACT-1154:
---------------------------------------------
> if we are using a tag to mark the release then why do we need to keep the
> branch as well?
I guess in theor on a branch named e.g. "1.4.x" we could cherry-pick fixes to
for a "1.4.1" release. In practice, I'm not really sure / doubt that anyone
(has the time to coordinate and) wants to do it. But we could still set it up
like that, just in case?
> have a "master" branch
Which shouldn't be literally called "master" anymore, with everything going on
in the world... see e.g. https://github.com/github/renaming.
> on which the releases are tagged - i.e. in line with this:
> [https://nvie.com/posts/a-successful-git-branching-model/]
I don't think I understand that - why not just tag on develop?
> 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)
