[
https://issues.apache.org/jira/browse/FINERACT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205067#comment-17205067
]
Aleksandar Vidakovic commented on FINERACT-1154:
------------------------------------------------
[~vorburger] sorry for the radio silence, missed the notifications for this
one. Yes, deleting the branch is a good idea... it only serves a purpose during
the release phase for backporting features from develop. If we wanted to create
hotfix/maintenance/patch releases (1.4.1, 1.4.2 etc.) we can still create new
branches based on the release tag and cherry pick the changes we need to
include.
So... let's get rid of those release branches.
> 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)
