Workflow of releases
'master' branch
We are planning next versioning scheme: 'master' branch has all features, bugfixes and other thinks. Nimeration is 'a.b.c'. For example, numeration of 'master' tags are:
- 4.7.0
- 4.7.1
- 4.7.2
- ...
Period of releases: two months.
'*-stable' branch
All changes contained in '*-stable' branch will also make it into the next release of the 'master' branch. The a.b.c.d release series will only contain bug fixes and stabilization patches. For example, numeration of tags are:
- 4.7.0.1
- 4.7.0.2
- ...
Period of releases: one month; or after 100 commits; or after critical bugfix.
This will continue until 'master' and '4.7.0-stable' branches will be compatible. At some time-point in future we will release out 4.8.0 and versioning scheme will repeated: for future 'master' branch:
- 4.8.0
- 4.8.1
- 4.8.2
- ...
and for future '4.8.0-stable' branch:
- 4.8.0.1
- 4.8.0.2 ...
We hope that this is good proposal for LTS-distros (it will be easy maintenance in downstream distros)...
