Wrapped up into this discussion is an (implicit) choice of a git workflow. See https://www.atlassian.com/git/tutorials/comparing-workflows
If I had to guess, I'd say that uimaFIT is following the feature branch git workflow: https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow The JGitFlow plugin seems appropriate if you have a project following the gitFlow workflow: https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow It probably would be a good idea to put into some central spot (say, for instance, in uima.apache.org, under perhaps a new page: Git_Workflows) something that describes the intended workflow for various kinds of contributors (e.g. committers, non-committers, etc), and various kinds of actions (doing a new feature, doing a "release", how releases are "tagged", etc.). -Marshall On 11/26/2018 4:26 PM, Richard Eckart de Castilho wrote: > On 26. Nov 2018, at 22:21, Marshall Schor <[email protected]> wrote: >> re: Maven JGitFlow Plugin - that sounds like quite a bit better approach for >> releasing, when on Git. > I don't see the benefit so far. It's surely hip, but I prefer the traditional > way with the Maven Release Plugin. > > Mind, I have no idea so far how to sensibly set up a Jenkins and deploy > SNAPSHOT builds to a Maven repo when using GitFlow. > > -- Richard
