Tim Schaub <tsch...@opengeo.org> writes: > I don't see real value in keeping around all of the old release > branches. If we were continuing to do releases in the 2.4.x series, > for example, the 2.4 branch would have a clear purpose. We can check > out release tags to run tests or do other work with a specific > release. Can anyone point to a clear purpose for keeping around the > old release branches? > > In case we do want to keep open the possibility of creating a patch > release from an old minor release, we could keep around two release > branches. My motivation for cleaning up old release branches is that > I like to run `git branch -avv` and the output is a bit ridiculous if > you have a couple remotes.
My opinion shouldn't count for much, but this seems like the wrong approach to me. Old release branches are history that may or may not be important, and it's hard to tell until they are later needed. It would seem relatively easy to write a (git alias|shell alias|etc.) to show what you want.
pgpKRoayR5Kmp.pgp
Description: PGP signature
_______________________________________________ Dev mailing list d...@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/openlayers-dev
