Ubuntu Development Processes (OLF2010)

Ubuntu Development Processes Mackenzie Morgan Developer Groups Ubuntu Development Processes The Release Cycle Making Changes Mackenzie Morgan Bugs Ohio LinuxFest 2010 UbuCon 10 September 2010

Outline Ubuntu Development Processes Mackenzie Morgan 1 Developer Groups Developer Groups The Release Cycle 2 The Release Cycle Making Changes Bugs 3 Making Changes 4 Bugs

Who are the developers? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Making Changes Bugs But that’s outdated

What changed? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Archive reorganisation (hereafter: archive reorg) Making Changes Bugs

What’s archive reorg? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle A switch away from components to a uniﬁed archive with Making Changes ﬁner-grained RBAC for uploading Bugs

Pre-Archive Reorganisation Ubuntu Development Processes Mackenzie Morgan 4 components: Developer Groups Main The Release Cycle Restricted Making Universe Changes Bugs Multiverse Core-devs upload to all of the above. Masters of the Universe (MOTU) upload to Universe & Multiverse

Post-Archive Reorganisation Ubuntu Development Packagesets: Processes Ubuntu Desktop Mackenzie Morgan Ubuntu Server Developer Kubuntu Groups Xubuntu The Release Cycle Mythbuntu Making Changes Ubuntu Studio Bugs Ubuntu Education Edition Ubuntu Mobile Kernel Network Manager Sugar Zope Correspond to packages on install discs

And those access controls. . . ? Ubuntu Development Processes Mackenzie Morgan Developer Groups Each packageset has a set of developers The Release Core devs still upload anything Cycle Making MOTU upload anything not in a package set Changes New: Generalist devs upload anything not in a restricted Bugs packageset New: Per-package uploaders

Where are we now? Ubuntu Development Processes Mackenzie Morgan Done: Developer Ubuntu Desktop Groups Ubuntu Server The Release Cycle Kubuntu Making Changes Mythbuntu Bugs Kernel Mono Mozilla Per-package uploaders

How many developers are there? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle 167 in ubuntu-dev Making Changes Unknown number of “prospective developers” Bugs

How do I ﬁnd a package’s maintainer? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle You don’t. We’re not Debian. Making Changes Bugs

What if you lack upload rights? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Other developers can sign oﬀ on and upload your package Making Changes (sponsoring) Bugs

How do you get upload rights? Ubuntu Development Processes Mackenzie Morgan Developer Groups 1 Do good work & get it sponsored The Release Cycle 2 Create a wiki page to apply Making Changes 3 Get sponsors to vouch for you on your wiki page Bugs 4 Go to a Developer Membership Board (or one of the delegated boards) meeting and get voted in

First things ﬁrst Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Binary-copy packages from previous release Cycle Making Automatically sync from Debian Sid (Testing if LTS) Changes Bugs Merge remaining packages

Stages Ubuntu Development Processes Mackenzie Morgan Developer Ubuntu Developer Summit Groups 3–4 Alphas The Release Cycle 1–2 Beta Making Changes 1–2 Release Candidates Bugs Ship it! Also, lots of freezes (Toolchain, Debian Import, String, UI, Feature, Final. . . )

What happens during freezes? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Uploads are queued pending Archive Admin approval Making Changes http://launchpad.net/ubuntu/maverick/+queue Bugs

Stable Release Upgrades (SRU) Ubuntu Development Processes Mackenzie Morgan Developer Groups Bugﬁxes only (preferably minimal patch) The Release Cycle Must document regression potential Making Upload to -proposed Changes Bugs Member of ubuntu-sru will approve the upload Moves to -updates after 2 weeks in -proposed

Packages are kept in VCS, like every other distro, right? Ubuntu Development Processes Mackenzie Morgan Developer Groups Er. . . yes and no. . . The Release Cycle Yes, all but ∼500 packages are in bzr now Making No, it hasn’t always been this way Changes Ubuntu Distributed Development (UDD) is the attempt at Bugs change

Why? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle We followed Debian on the debuild -S && dput Making Changes ../*.changes thing Bugs

Why change? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Debian has only a few maintainers per package Making Changes We have team maintainership, >70 developers responsible Bugs

How’s the change going? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Slowly. Making Changes Bugs

Why slowly? Ubuntu Development Processes Mackenzie Morgan Developer We have (thanks mostly to James Westby): Groups The Release tools (mostly) Cycle Making docs (mostly) Changes branches (mostly) Bugs

Why slowly? Ubuntu Development Processes Mackenzie Morgan Developer We have (thanks mostly to James Westby): Groups The Release tools (mostly) Cycle Making docs (mostly) Changes branches (mostly) Bugs Have you ever tried to convince 150 people to stop doing what seems to work and learn something new?

Old workﬂow Ubuntu Development Processes Mackenzie Morgan Developer apt-get source foo Groups The Release cd foo Cycle Making Make changes & add changelog entry Changes debuild -S Bugs Use pbuilder to test-build ../*.dsc dput foo*.changes

New workﬂow Ubuntu Development Processes bzr branch lp:ubuntu/foo or bzr branch Mackenzie Morgan lp:ubuntu/hardy/foo cd foo Developer Groups Make changes & add changelog entry The Release Cycle bzr-buildpackage -S Making Changes Use pbuilder to test-build ../*.dsc Bugs debcommit debcommit generates changelog entry Then it diverges. . . If the team merges many changes then releases: bzr push If not: dput ubuntu ../*.changes && bzr mark-uploaded && bzr push No, there’s no automated “build this branch” button yet

How do I report a bug? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release apt-cache policy package Cycle If package version shows Debian/Ubuntu changes: Making Changes ubuntu-bug package Bugs If not or if clearly not a packaging bug, report it upstream

How are patches handled in Ubuntu? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Badly. Making Changes Bugs

Why? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release “Not enough monkeys” Cycle – Daniel T. Chen Making Changes Bugs ∼2000 patches bitrotting in Launchpad

What’s being done about it? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Operation Cleansweep Making Changes Ubuntu Reviews team Bugs

Operation Cleansweep Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Try to review all patches & forward the good ones before Making 10.10 is released Changes https://wiki.ubuntu.com/OperationCleansweep Bugs

Reviews Team Ubuntu Development Processes Mackenzie Morgan Developer Groups Ubuntu Reviews team formed to: The Release Cycle review patches Making upstream patches if needed Changes Bugs run Patch Days http://launchpad.net/∼ubuntu-reviews

How can I submit a patch? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Attach it to the bug report Cycle Mark it as a patch on upload Making Changes Add the “patch” tag to the bug Bugs Submit it upstream too!

Can I use the bzr branches from before? Ubuntu Development Processes Mackenzie Yes! Morgan If making a new candidate revision: Developer In debian/changelog: LP: #12345 Groups The Release debcommit Cycle bzr push lp:me/foo/fixfor12345 Making Changes If not: Bugs bzr commit --fixes 12345 Fill in a changelog entry bzr push lp:me/foo/fixfor12345 Branch is automatically linked to bug report bzr lp-open to submit merge proposal

Can I submit a debdiﬀ like in Debian? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Yes! Making Subscribe ubuntu-sponsors to the bug report (and still include Changes LP: #12345 in debian/changelog) Bugs

What’s that LP: #12345 stuﬀ? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Bug #12345 will be automatically marked Fix Released when Making Changes the package is uploaded Bugs

Why so many bugs in stable? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Testing happens too late (Beta) Cycle Making Rushing to ﬁx bugs late introduces more bugs Changes Bugs Need more developers

Questions? Ubuntu Development Processes Mackenzie Morgan Developer Groups The Release Cycle Making Changes Bugs

http://ubuntulinuxtipstricks.blogspot.com	393
http://www.linuxplanet.org	25
http://ubuntulinuxtipstricks.blogspot.in	7
http://ubuntulinuxtipstricks.blogspot.de	7
http://ubuntulinuxtipstricks.blogspot.co.uk	3
http://ubuntulinuxtipstricks.blogspot.ca	3
http://translate.googleusercontent.com	2
http://ubuntulinuxtipstricks.blogspot.com.es	2
http://ubuntulinuxtipstricks.blogspot.fr	2
http://ubuntulinuxtipstricks.blogspot.com.au	2
http://ubuntulinuxtipstricks.blogspot.mx	2
http://ubuntulinuxtipstricks.blogspot.it	1
http://ubuntulinuxtipstricks.blogspot.pt	1
http://ubuntulinuxtipstricks.blogspot.com.ar	1
http://www.grandy-net.blogspot.com	1
http://www.gnarc.com	1
http://static.slidesharecdn.com	1
http://ubuntulinuxtipstricks.blogspot.com.br	1

Ubuntu Development Processes (OLF2010)

by Mackenzie Morgan on Sep 10, 2010

Accessibility

Categories

Tags

Upload Details

Usage Rights

18 Embeds 455

Statistics

Ubuntu Development Processes (OLF2010) — Presentation Transcript