On Wed, 9 Feb 2011, Mounir Bsaibes wrote:
On Wed, Feb 9, 2011 at 9:53 AM, Nicolas Pitre nicolas.pitre@linaro.orgwrote:
Here's what I intend to do with regard to the Linaro kernel to be used for the 11.05 release.
I'll create a linaro-2.6.38 tree which will be seeded with v2.6.38-rc5 which should happen sometimes next week. That will be about the same level of functionality as what we currently have in linaro-2.6.37 for the ARM parts, and merging the remaining extra patches found in linaro-2.6.37 not to be found in 2.6.38 yet should be quite easy.
So if you have more patches that you want to see included in the 11.05 Linaro release then it is a good thing to rebase them to the latest mainline (currently 2.6.38-rc4) and make sure they are validated and sent my way _before_ February 24th. Incidentally, while at it, this would also be a good time to send those patches to the respective upstream maintainers for inclusion into the mainline kernel tree during the upcoming merge window.
Thank you for the info, this is clear. Can we generalize this for future releases, so we know what to do at the Feature freeze time frame?
I'm afraid this might be hard to formalize as the timing with the upstream kernel release is likely to always be different, which might require a judgment call each time.
This time we can say that I'll open the Linaro 2.6.38 branch sooner than usual if we want to refer to the kernel maintenance process documentation I produced.
And none of our previous 2 releases went the same way, this one is going to be also different, so that's a sign that we might not be ready to formalize a process yet.
What happens after the February 24th?
Only bug fixes are accepted in the linaro-2.6.38 kernel tree and a new one is created for tracking latest developments, except that I won't be able to call the new branch linaro-2.6.38. Or maybe I'll simply fork the frozen kernel for the 11.05 release, calling it linaro-11.05 and keep moving ahead with linaro-2.6.38.
Nicolas