17 Apr
2015
17 Apr
'15
6:03 p.m.
On Friday 17 April 2015 18:32:45 Sven Eckelmann wrote: [...]
Releases
I was also under the impression that no one really knew what will be released and what version of the kernel tree it will be based on. How about changing the Release-todo (see attached image) * maint branch is released as feature release 2015.a after linux 4.x is tagged * 2015.a.y branches are released on demand... most likely never * content of master becomes new maint after release
Meant was "content of master becomes new maint after current maint was released".
It may also be important to understand that new features in master after the net-next.git merge window closed should not become part of the new maint because they cannot be pushed to David for the next 4.x version. But this is not a real technical problem because the maint must not really jump to the latest position of the master branch HEAD - it is possible to choose a slightly older position and still get a fast-forward merge in git.
Kind regards, Sven