[MinGW-dvlpr] RFC: Repository workflow - branches and tags

[Earnie B. <ea...@us...>]

I'm currently thinking about mingw.org-wsl but this may apply to other
repositories as well.

* The master branch is the baseline and should contain only known working code.
* A branch is created that represents the next version release as a
working release, e.g 4.0-dev.
* A tag is created that represents the released version, e.g 4.0.
* The working branch should be merged to the master branch just prior
to release and tagging.
* A feature freeze (typically 2 to 4 weeks prior to planned release
date) would result in a new branch tag representing the next release
+1, e.g. 4.1-dev.
* The working branch should be merged to the master branch just prior
to the feature freeze.
* The master branch should be merged to the next release + 1 branch
just after a new release making it the new working branch.
* The previous working branch is removed from the repository leaving
the current working branch.

-- 
Earnie
-- https://sites.google.com/site/earnieboyd