Hello!
The February 24th feature freeze is coming up very quickly. We therefore need any kernel patches that are to be included into the 11.05 Linaro kernel release to be submitted to linaro-dev (CCing nicolas.pitre@linaro.org) as well as upstream as soon as possible. Otherwise, we cannot guarantee that they will be included in the upcoming Linaro kernel release.
Thanx, Paul
On Monday 07 February 2011, Paul E. McKenney wrote:
The February 24th feature freeze is coming up very quickly. We therefore need any kernel patches that are to be included into the 11.05 Linaro kernel release to be submitted to linaro-dev (CCing nicolas.pitre@linaro.org) as well as upstream as soon as possible. Otherwise, we cannot guarantee that they will be included in the upcoming Linaro kernel release.
I suppose by submitting upstream, you mean that the patches need to show up in one of the trees that are part of linux-next, right?
The development phase for 2.6.38 is closed, and the merge window for 2.6.39 will not be open until the Linaro feature freeze, so that is the only place where patches heading for upstream can go at the moment.
Arnd
[ Added linaro-dev for a wider diffusion ]
On Wed, 9 Feb 2011, Arnd Bergmann wrote:
On Monday 07 February 2011, Paul E. McKenney wrote:
The February 24th feature freeze is coming up very quickly. We therefore need any kernel patches that are to be included into the 11.05 Linaro kernel release to be submitted to linaro-dev (CCing nicolas.pitre@linaro.org) as well as upstream as soon as possible. Otherwise, we cannot guarantee that they will be included in the upcoming Linaro kernel release.
I suppose by submitting upstream, you mean that the patches need to show up in one of the trees that are part of linux-next, right?
The development phase for 2.6.38 is closed, and the merge window for 2.6.39 will not be open until the Linaro feature freeze, so that is the only place where patches heading for upstream can go at the moment.
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.
Nicolas
On Wed, Feb 9, 2011 at 9:53 AM, Nicolas Pitre nicolas.pitre@linaro.orgwrote:
[ Added linaro-dev for a wider diffusion ]
On Wed, 9 Feb 2011, Arnd Bergmann wrote:
On Monday 07 February 2011, Paul E. McKenney wrote:
The February 24th feature freeze is coming up very quickly. We
therefore
need any kernel patches that are to be included into the 11.05 Linaro
kernel
release to be submitted to linaro-dev (CCing nicolas.pitre@linaro.org) as well as upstream as soon as possible. Otherwise, we cannot
guarantee
that they will be included in the upcoming Linaro kernel release.
I suppose by submitting upstream, you mean that the patches need to show up in one of the trees that are part of linux-next, right?
The development phase for 2.6.38 is closed, and the merge window for
2.6.39
will not be open until the Linaro feature freeze, so that is the only place where patches heading for upstream can go at the moment.
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? What happens after the February 24th?
Nicolas
linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
On 02/09/11 at 03:03pm, Mounir Bsaibes wrote:
On Monday 07 February 2011, Paul E. McKenney wrote:
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? What happens after the February 24th?
We continue to accept changes on case-by-case basis allowing for any obvious exceptions. The Feature Freeze is considered a soft-freeze, it can be broken but it has to be acknowledged by the Release Team and should be the exception rather than the norm.
https://wiki.linaro.org/Process/DevelopmentCycle#Stabilization (Freeze)
has some good information.
Regards, Jamie. -- Linaro Release Manager | Platform Project Manager Office: +44 1761 348 220 | Mobile: +44 7962 259 437
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
On Wed, 2011-02-09 at 16:36 -0500, Nicolas Pitre wrote:
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.
I prefer the latter plan. Fork a frozen kernel, call it linaro-11.05, and keep moving ahead with linux-linaro-2.6.38. It makes it easier to explain how our kernel git tree management works to members (and I do this a lot).
Scott
On Wed, 9 Feb 2011, Scott Bambrough wrote:
On Wed, 2011-02-09 at 16:36 -0500, Nicolas Pitre wrote:
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.
I prefer the latter plan. Fork a frozen kernel, call it linaro-11.05, and keep moving ahead with linux-linaro-2.6.38. It makes it easier to explain how our kernel git tree management works to members (and I do this a lot).
Good! I'll update the Linaro kernel maintenance documentation with this.
Nicolas
linaro-kernel@lists.linaro.org
-
Arnd Bergmann -
Jamie Bennett -
Mounir Bsaibes -
Nicolas Pitre -
Paul E. McKenney -
Scott Bambrough