+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 recreate them if needed from the last commit. On Tue, Jun 7, 2016 at 7:58 AM, Andre <[email protected]> wrote: > 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 > - journaling-prov-repo - markap14 - (Mar 2015) - Suspect it is NIFI-388 > - prov-query-language - markap14 (Mar 2015) - Suspect it is NIFI-40 > - ListHDFS - markap14 (Apr 2015) - Suspect it is NIFI-533 > > Branches for resolved tickets > - Issue (Resolved date) > - NIFI-25 (Apr 2015) > - NIFI-259 (Feb 2016) > - NIFI-274 (Nov 2015) > - NIFI-376 (Aug 2015) > - NIFI-433 (May 2015) > - NIFI-631 (Nov 2015) > - NIFI-640 (July 2015) > - NIFI-655 (Dec 2015) > - NIFI-730 (Nov 2015) > - NIFI-731 (Jul 2015) > - NIFI-744 (Aug 2015) > - NIFI-810-InputRequirement (Oct 2015) > - NIFI-919 (Sep 2015) > - NIFI-1073 (Nov 2015) > - NIFI-1085 (Nov 2015) > - NIFI-1107 (Feb 2016) > > > Branches with Open tickets > - Issue - Owner (Last update) > - NIFI-725-master - Dan Bress (Aug 2015) > - NIFI-818 - Mark Payne (Nov 2015) > - NIFI-964 - Bryan Bende (Nov 2015) > - NIFI-1050 - 65534 (Oct 2015) > - NIFI-1563 - Mark Payne (Apr 2016) > > > Branches with heavy development ongoing (probably should leave there...) > - NIFI-1323 - 65534 (Jun 2016) > > > Note that although I suspect the releases are published under tags, the > list above does not include what seem to be RC branches, > > > > *Remember* that keeping things tidy help the project look professional. :-P > > > Jokes aside may I suggest someone spend some time cleaning some of these > branches? > > Wouldn't mind doing it myself but I don't have write access :-) > > Cheers >
