Stable derivative branch handling

Paolo Pisati paolo.pisati at canonical.com
Mon Jun 13 14:02:22 UTC 2011


On 06/13/2011 03:46 PM, Andy Whitcroft wrote:
> 
> 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


what about all the others non-rebasable branches?

so far there's only one arm rebasable branch (lucid/mvl-dove) vs 4 arm
branches (lucid/imx51, [maverick|natty|oneiric]/ti-omap4) that need to
be manually maintained, but i don't think we can do much about them (and
i fear the number of these branches will increase in the future).

other than that, i'm ok with it.
-- 
bye,
p.




More information about the kernel-team mailing list