Understanding the Dapper Drake Development Process
My first day at the Ubuntu Developers Conference (UBZ) has been a lot of work and a lot of fun.
There are a few key decisions going into the next release cycle that inform everything else.
As I mentioned yesterday the next version of Ubuntu is going to be supported for a long time. In order to make that happen, the Ubuntu Distribution team is going to make a couple of minor changes to the release process. Most of these come under the basic theme of minimizing large scale changes.
Earlier on in the discussion of the Dapper process Jeff Waugh suggested the possibility of not syncing up to the latest stuff in Debian unstable on this cycle, and just moving forward from 5.11 base. The idea behind this suggestion was to limit the number of unknown bugs that would be added to the distribution. However, Matt Zimmerman pointed out that ” Debian and upstream fix more bugs than we do, hands down” so this idea has been rethought a bit.
That said, there is going to be an overall reduction in the number of new crazy things going into Ubuntu. But as of last night there will be one major exception — the LiveCD based installer.
This is making it in, not just because it will make the user experience better, but also because with a LiveCD installer Ubuntu will only have to ship one CD through ship-it. And that in turn means they will be able to support more than one flavor of Ubuntu. This means that they will be shipping Kubuntu cd’s for all the KDE centric folks out there.
But all of that comes from this morning’s first talk, and since then I have been participating mostly in talks about Ubuntu Server stuff, and I’ll try to blog about that more soon.
0 Responses to “Understanding the Dapper Drake Development Process”