Ok, I'm +1 to this as well. Jira and our Git history does anything we need for posterity (aside from those wanting to re-live old feature branch glory days - who am I to judge?), so no need for the extra cruft. I've participated on but not created a FB yet - is it an infra request to deal with the CUD part of CRUD on a FB?
On Fri, Sep 7, 2018 at 11:20 AM zeo...@gmail.com <zeo...@gmail.com> wrote: > Yeah I don't have a good reason to suggest we keep 'em. so +1 to deleting > old FBs. > > Jon > > On Fri, Sep 7, 2018 at 12:14 PM Nick Allen <n...@nickallen.org> wrote: > > > +1 delete old feature branches. > > > > BTW, there is a branch out there called METRON-113 that we probably need > to > > clean-up. I'm not sure where that came from or why its still around. > > Probably a fat-finger from long ago. > > > > On Fri, Sep 7, 2018 at 12:00 PM Otto Fowler <ottobackwa...@gmail.com> > > wrote: > > > > > I would drop them. > > > I’ve already clean up FB’s around dead things. > > > > > > > > > > > > On September 6, 2018 at 13:42:55, Michael Miklavcic ( > > > michael.miklav...@gmail.com) wrote: > > > > > > What are we doing with feature branches once they're complete and > merged > > > into master? Is our expectation that we'll keep feature branches in > > > perpetuity, or should we plan to do some house cleaning once they've > been > > > merged? I did a quick check of NiFi and Kafka and don't see much by way > > of > > > feature branches in their repos. I see plenty of RC's in both the > > branches > > > and tags listings, but nothing FB related. In previous discussions, we > > > talked quite a bit about us "trailblazing here," so it may be that this > > is > > > simply without much precedent and entirely for us to decide. I can > > > definitely see value in maintaining them for future reference, as it > does > > > offer a nice bucket in which to collect the commits and discussion > > nicely, > > > but I wanted to get others' thoughts. > > > > > > Best, > > > Mike > > > > > > -- > > Jon >
