[Skiboot] op-build: new branch master-next

[Patrick Williams III]

With the release of op-build v1.0, I created a new branch to prepare for v1.1 called 'master-next'.  This allows us to easily make v1.0.x releases on top of v1.0 to fix critical problems until v1.1 is released without having to create and manage a branch for every release.

My intention is that master-next can always be seen as the "release candidate" for the next op-build release.  In order to accomplish this, all pull requests for new functionality should go against the master-next branch.  Only critical fixes for an existing release, such as v1.0, should go into master.

We should be doing additional releases on a fairly regular cadence for the foreseeable future.  I suspect this will be somewhere between 2 weeks and a month.  Near the point of release, we will take everything from 'master-next' and merge it into 'master' and create a tag on 'master' for the next release.  I say 'near' because I haven't decided if we will create formal -rc tags and if they should be on master or master-next.  If you have an opinion, please let me know.

Patrick Williams
Power Firmware Development, 
Bldg 045-2/C034
512-286-6369, T/L: 363-6369
iawillia at us.ibm.com