Mailing-List: contact dev-help@nifi.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@nifi.apache.org
MIME-Version: 1.0
In-Reply-To: <CALJK9a6KpQnmMneY5T=EgPKF16q6OwzD=03PFxr6AWxwmmgpjw@mail.gmail.com>
References: <CAJpGy9Lrm=xt7Y7J_xmatdGogZZXnQ0QOby0vV20S4sJnN06VQ@mail.gmail.com>
	<CAPYoqXR0vFP1sGK+5imjs6gThP-d-kUF018Tj7MR4cqEOaiDVA@mail.gmail.com>
	<CALJK9a6KpQnmMneY5T=EgPKF16q6OwzD=03PFxr6AWxwmmgpjw@mail.gmail.com>
Date: Fri, 22 Jul 2016 08:26:21 +1000
Message-ID: <CAJpGy9L4b+iZBg0eEoCO=VeqaVcwqDXbGLx0XVNBy=np6HuPWQ@mail.gmail.com>
Subject: Re: Git branch clean-up
From: Andre <andre-lists@fucs.org>
To: dev@nifi.apache.org
Content-Type: multipart/alternative; boundary=94eb2c1936f6c8e6de05382cceb2
archived-at: Thu, 21 Jul 2016 22:26:29 -0000

--94eb2c1936f6c8e6de05382cceb2
Content-Type: text/plain; charset=UTF-8

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" <joe.witt@gmail.com> wrote:

> 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" <jskora@gmail.com> wrote:
>
> > +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 <andre-lists@fucs.org> 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
> > >
> >
>

--94eb2c1936f6c8e6de05382cceb2--