[
https://issues.apache.org/jira/browse/FINERACT-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17207698#comment-17207698
]
Petri Tuomola commented on FINERACT-1154:
-----------------------------------------
Hi [~vorburger] - very happy to keep things as simple as possible, but just to
share my concerns re "not merging back from release branches":
# As your experiment also pointed out, things had already got out of synch
between develop and 1.4.0. Hopefully these are all minor things but I'd like to
be 100% sure that the release branch is properly "empty".
# Personally I like "git describe" to provide a meaningful output that we can
use to automatically populate version numbers etc. With the current approach it
will say "1.3.0-xyz-123" forever (as 1.3.0 is the last release tag reachable
from develop)
# It can also be helpful with troubleshooting to see what are the commits
since last release. With the tag not visible in the develop changelog, it's
impossible now to see when in the history the last release was - i.e. what are
the changes since 1.4.0 etc
Just my thoughts... but maybe I'm the only one bothered by this!
> 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: Petri Tuomola
> 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)
