Stable derivative branch handling

[David Henningsson]

On 2011-06-13 15:46, Andy Whitcroft wrote:
> After some discussion on IRC it was decided that it is time we formalised
> the process for derivative branches and the interactions between the core
> team and the domain experts for preparing kernels for release, such that we
> have formal checkpoints in the stable cadance to ensure that the derivative
> branches are updated when required but do not prevent forward progress.
>
> To this end once the main distro kernel tree are prepared the kernel
> stable team will announce their availability to the derivative branch
> maintainers.  This will indicate that the master branches are now ready
> for rebasing onto where that is appropriate.  The derivative maintainers
> will then rebase if required and determine if their branch has anything
> worthy of an upload.  If so they will reply to the announcement adding
> their branch to the versions to pushed this cycle.  The stable team will
> then handle closing and uploading this branch with the main branches.
> If the derivative branches are not ready in time for upload, they will
> simply slip to the next cadance round.
>
> The current derivative branch maintainers are:
>
>   - smb: Lucid -ec2
>   - ppisati: everything arm
>
> Comments?

Is this relevant/helpful for maintaining other kernels (e g the 
lowlatency stuff comes to mind), or is that a completely orthogonal 
problem to this one?

-- 
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic