You can change the default GitHub exposed branch in the GitHub options. Pointing it at stable for new commers and leaving master as it is.
On Thursday, 8 September 2016, John Haddon <[email protected]> wrote: > For what it's worth, I prefer #1, for the same reasons of simplicity and > linearity of history that you cited. > > I'm not convinced that #2 is easier for new folks either. It does mean > that their first build will be of a stable production release, but it also > means they need a deeper knowledge of git and github to get to the point of > making a first PR. If I just want a stable build of a project (rather than > to develop on it), I'll always pull down a source tarball for a specific > known version rather than `git clone` anyway… > > Cheers… > John > > ________________________________________ > From: Oiio-dev [[email protected] <javascript:;>] on > behalf of Larry Gritz [[email protected] <javascript:;>] > Sent: Thursday, September 08, 2016 10:29 AM > To: OpenImageIO developers > Subject: [Oiio-dev] Branch naming poll > > There seem to be two ways people develop in Git repos: > > 1. Develop in "master", and branch/tag stable releases -- this is what we > do, and we name release branches RB-x.y and tag specific releases > Release-x.y.z, and we also have a branch called "release" is moved around > to always point to the latest approved release tag. > > 2. Have "master" always point to an approved release (replacing our > current "release" branch label), and have a "dev" branch that is the top of > the development tree. So a release consists of moving the "master" marker > (and/or merging dev into it). > > _______________________________________________ > Oiio-dev mailing list > [email protected] <javascript:;> > http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org >
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
