KernelFreeze, 2.6.14, UBZ agenda, and other bits

Ben Collins ben.collins at ubuntu.com
Fri Sep 30 21:35:41 UTC 2005


2.6.12-9.19 is being upload as I write this email. With this release, we
are in KernelFreeze (yes, I know it was yesterday, but this release needed
to go out).

So that means Breezy kernel will be treated almost like hoary's kernel as
of now, with probably a few exceptions on a case-by-case basis.

On to 2.6.14, for dapper. I've already got a tree in baz for 2.6.14, but
before we go head strong into it, I think we need to re-evaluate the whole
kernel development proces for Ubuntu. UBZ is probably going to be a good
time for us to finalize some ideas for this. I wasn't here for most of
breezy, so I don't know all the problems or things learned from the last
cycle. This is where most of you step in.

I want to get an agenda setup for discussion at UBZ, mainly to outline our
development cycle for post-breezy and 2.6.14. The main thing on the top of
my list right now is RCS. If anyone has anything to add to it, let me
know.

We've some conflicts about some of our objectives for the kernel. First
off, Matt wanted me to get the kernel onto kernel.org as a more open and
public development line. However, with all of our internal work, I feel
like baz/bzr is the required revision control system.

If we want to be more apart of the kernel development, then we need to
move to git. My thinking was that we would host the git tree on our
system, and push a copy of it to kernel.org on a regular basis (few times
a day if needed) for people to pull from.

Personally, I'm all for moving to git. However, I understand that Ubuntu
as a whole also need to be concerned with consistency, and git isn't
consistent with some of the future goals.

So what I may propose is a dual RCS. Use git for our kernel tree, in which
we will integrate the mainline kernel with external drivers and
siginificant patchsets. Then use baz for our debian/ directory like we do
now, which will also hold patches, but will be the ones that are ubuntu
specific (hacks and workarounds, and such).

-- 
   Ben Collins <ben.collins at ubuntu.com>
   Developer
   Ubuntu Linux




More information about the kernel-team mailing list