Re: Git branch clean-up

Any branches I created can be deleted On Sep 26, 2016 11:57 AM, "Joe Witt" wrote: > Andre > > The support branch for 0.7 would happen if there were a incremental > release for it. > > The tags represent the exact released bits (version values are > set/etc..). The

Re: Git branch clean-up

Andre The support branch for 0.7 would happen if there were a incremental release for it. The tags represent the exact released bits (version values are set/etc..). The support/RC ones have the correct snapshot/etc.. on them. The items that are quite old are probably fair game to cleanup.

Re: Git branch clean-up

All, Clean-up is almost done, but I have a question. Would anyone have a suggestion on what to do with the multiple RC branches? We currently have some inconsistency around version related branches, with branches like "support/nifi-0.6.x" or even "release-nifi-0.1.0-rc13" but no branch like

Re: Git branch clean-up

All, Seems like we are making some progress around this. Some of the branches have been already deleted and some more have been documented and deleted. The following branches belong to closed ticket but had commits ahead of master and were left behind until we clarify they are safe to delete

Re: Git branch clean-up

Devs, I was wondering if anyone had any success deleting the stalled remote branches? Should we perhaps add the clean up as part of 1.0s the release cycle? Cheers On 7 Jun 2016 22:42, "Joe Witt" wrote: > Definitely agree with the spirit of this thread. I am happy to do a

Re: Git branch clean-up

Definitely agree with the spirit of this thread. I am happy to do a purge on clearly dead branches. Of note there was a decent chunk of time where we could create branches but not remove them. Thanks. Joe On Jun 7, 2016 8:25 AM, "Joe Skora" wrote: > +1 for cleaning up the

Re: Git branch clean-up

+1 for cleaning up the *Branches for resolved tickets* group. The other groups should probably be reviewed by the last committers and removed if appropriate. A Jira ticket (or tickets) identifying each branch and its last commit hash will document their removal while also making it easy to

Git branch clean-up

Devs, It seems like the git tree is filled with stagnated / legacy branches covering issues that have been already resolved. Unclear ticket number Branch name - last committer (date) - Suspected related issue - improve-prov-performance - mcgilman (Apr 2015) - suspect it is NIFI-524 -