Ubuntu Wiki

Include(UbuntuDevelopment/Header/Menu)

Anchor(Overview)

Overview of Development

Ubuntu is developed by a team of UbuntuDevelopers. There are two types of UbuntuDevelopers: [http://launchpad.net/~ubuntu-core-dev core developers] and [http://launchpad.net/~motu MOTU]. This process is transparent to the public, and open to any contributor who demonstrates the necessary skills and commitment to the project.

Ubuntu is based on [http://www.debian.org/ Debian], sharing many of its packages, tools and techniques with that project. Differences between Ubuntu and Debian are described in UbuntuForDebianDevelopers.

Ubuntu is [:/ReleaseProcess:periodically released] according to a set schedule.

Like most operating systems, Ubuntu is complex, and it can help to get a broad overview of its architecture first. For that, see UbuntuArchitecture.

If you have been directed to this page for advice on contributing to Ubuntu as a developer, you may also be interested in ContributeToUbuntu.

Anchor(OtherDevelopers)

Working with Other Developers

You are not alone! Ubuntu is the work of many developers, and we devote some effort to enabling efficient collaboration with tools, infrastructure, government and a cooperative spirit.

Anchor(StartingPoints)

Starting points

UbuntuDevelopers explains the role of developers in the Ubuntu project and how to join the team.

The [:MOTU] team, in addition to their development activities, provide information and guidance for new and prospective Ubuntu developers. If you're newly interested in Ubuntu development and looking for answers, introduce yourself and listen in!

If you're looking for tasks which need doing, many of those are tracked in the bug tracking system. The BugSquad maintains several lists of them at ["Bugs/Tags"].

If you already have experience working with Debian packages, most of your knowledge applies equally well to Ubuntu packaging. If you are a Debian developer, UbuntuForDebianDevelopers summarizes some of the differences between the projects, and later sections in this document provide details of our infrastructure.

To submit patches for review or to help reviewing patches, please refer to [:/CodeReviews:the Code Review process].

Anchor(Communication)

Communication

Email discussion among Ubuntu developers takes place on the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel ubuntu-devel mailing list], which is moderated (excepting registered Ubuntu developers). The [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss ubuntu-devel-discuss mailing list] is available for open discussion about Ubuntu development. All UbuntuDevelopers should subscribe to the [http://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-announce ubuntu-devel-announce mailing list], where important development events are announced. [https://lists.ubuntu.com/mailman/listinfo/ Various other mailing lists] are available, some of which focus on specific areas of development.

The #ubuntu-devel channel on the FreeNode IRC network is home to many Ubuntu developers for real-time communication.

[:/PackageArchive#Notification:Automated notifications of development activity] are also useful for keeping up with what other developers are working on.

A comprehensive matrix of communication channels can be found on DeveloperCommunication.

Anchor(Bugs)

Bugs and the BugSquad

[http://bugs.launchpad.net/ubuntu Ubuntu bug reports] are tracked in Launchpad. HelpingWithBugs contains information about how they are handled. The BugSquad documentation describes how to cooperate with other developers and volunteers working on bug triage; it is required reading for new developers, as developers will typically need to spend a significant amount of time working with the bug tracking system.

The BugSquad (and the Ubuntu Bug Control team, which is comprised of more experienced triagers who can prioritize bugs) are here to help you as a developer. If you are responsible for a non-trivial number of bugs, it is a good idea to spend some time on helping them help you. A useful starting point is to add specific information about your packages to DebuggingProcedures: this may include both special tricks for debugging them effectively and any particular policy you have on how you want your bugs to be handled (e.g. assignment, tags, etc.). When adding significant chunks of new information to DebuggingProcedures, please send a note to ubuntu-bugsquad@lists.ubuntu.com about it.

Members of the Bug Squad can be found on the #ubuntu-bugs channel on the FreeNode IRC network. There is also the [https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugsquad ubuntu-bugsquad mailing list] for general discussion regarding bugs and bug triaging.

Anchor(RCBugs)

Release Critical bugs

• [https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.importance%3Alist=Critical&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_contact=&field.milestone%3Alist=200&field.component=1&field.component=2&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_cve.used=&field.has_no_package.used= Showstopper bugs] Critical and milestoned to the relevant release. Those bugs will hold up the release if not fixed.

• [https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-importance&search=Search&field.status%3Alist=Unconfirmed&field.status%3Alist=Needs+Info&field.status%3Alist=Confirmed&field.status%3Alist=In+Progress&field.status%3Alist=Fix+Committed&field.importance%3Alist=High&field.importance%3Alist=Critical&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_contact=&field.milestone%3Alist=200&field.component=1&field.component=2&field.component-empty-marker=1&field.status_upstream=&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.tag=&field.has_cve.used=&field.has_no_package.used= Release-critical bugs] Critical and high importance bugs milestoned to the relevant release. Those bugs need to be fixed or worked around/documented before the release.

Anchor(ReleaseProcess)

The Release Process

Find all Release Management related information [:UbuntuDevelopment/ReleaseProcess:here]

Anchor(Packaging)

Packaging

If you're interested in packaging work, but don't have much experience yet, you should read [:MOTU/GettingStarted:this] to get involved in the ["MOTU"] team.

Anchor(DebianPackages)

Working with Debian-format Packages

Ubuntu uses the Debian packaging format. The following resources explain how to create and modify Debian-format packages.

• If you are already familiar with Debian development, UbuntuForDebianDevelopers explains some of the differences between the projects.

• All Ubuntu developers should be familiar with the [http://www.debian.org/doc/maint-guide/ Debian New Maintainer Guide] and the [http://www.debian.org/doc/debian-policy/ Debian Policy Manual]; though be aware that there are many differences (technical, social and procedural) between Ubuntu and Debian of which they must also be aware.

• [:PackagingGuide:The Ubuntu Packaging Guide]

• [http://women.debian.org/wiki/English/PackagingTutorial A packaging tutorial] is available from the Debian Women project, as is [http://women.debian.org/wiki/English/MaintainerScripts an explanation of maintainer scripts] and [http://women.debian.org/wiki/English/AdvancedBuildingTips further help with building packages].

• Many packages use tools to help manage multiple patches. [:PackagingGuide/PatchSystems:Patching Ubuntu packages] explains how to work with them.

  • The [https://perso.duckcorp.org/duck/cdbs-doc/cdbs-doc.xhtml CDBS Manual] explains how to work with packages using the CDBS packaging scripts, one example of a patch system (and more)

• Packaging shared libraries is a delicate task, and getting it wrong can cause upgrade headaches for users. The [http://www.netfort.gr.jp/~dancer/column/libpkg-guide/libpkg-guide.html Debian Library Packaging Guide] can be useful in avoiding some of the common traps.

• For a deeper understanding of the packaging process, you might want to have a look at this one: http://women.debian.org/wiki/English/BuildingWithoutHelper

• http://people.debian.org/~calvin/unofficial/ contains information on maintaining your own archive of unofficial packages.

• [https://lists.ubuntu.com/archives/ubuntu-motu/2006-February/000443.html how to write watch files] for sourceforge.net hosted projects

Anchor(UbuntuPackages)

Working with Ubuntu Packages

• Set the target suite in debian/changelog to be the code name of the current development branch, e.g. "dch -D gutsy"

• When working with a package which originated in Debian, use a version number derived from the Debian version number with ubuntu<revision> appended. e.g. Debian 1.0-2 becomes 1.0-2ubuntu1, followed by 1.0-2ubuntu2, etc.

• When creating a new package which may later be added to Debian, use a revision of the form -0ubuntu1

• Remember to include the orig.tar.gz if this is a new upstream version of a non-native package but you have already patched it before upload. A missing original tarball may cause the upload to be rejected or silently dropped. Use dpkg-buildpackage -S -sa to generate such an upload. If the orig.tar.gz is already in the distribution then you don't need to upload it again.

• Always be aware of the release schedule and any applicable [:/ReleaseProcess#Freezes:freezes]. The cooperation of all developers is needed in order to ensure a successful release!

• If your changes may affect the work of other developers, it is a good idea to discuss them on a mailing list first

Anchor(Bazaar)

Revision control (Bazaar)

Bazaar, an open source revision control system and Canonical sponsored project, is the preferred revision control system in Ubuntu. Many Ubuntu packages are [:BzrMaintainerHowto:maintained in Bazaar], which makes it easy for other developers to [:BzrContributorHowto:contribute changes to them], which can be easily merged by the maintainer.

Note that, as a practical matter, many packages are not yet maintained in Bazaar, but in other revision control systems or none on a case-by-case basis. Where no revision control system is used, the history of uploads recorded in [https://launchpad.net/ubuntu/+search Launchpad] may be useful.

Anchor(Derivatives)

Derivative Distributions

Several derivatives of Ubuntu are available (also sometimes called "flavours"). A number of people in the Ubuntu community work on one or more of these derivative versions. Kubuntu, Edubuntu, and Xubuntu are all maintained directly in the Ubuntu archive.

• [:KubuntuPackagingGuide]

Anchor(Building)

Building

You should always build and test packages locally before submitting them to Ubuntu. Failure to do so will waste the time of other members of the community, so please be considerate.

• You may want to build them in a [:DebootstrapChroot] or in [:PbuilderHowto:pbuilder]

• Backports are explained at [:BackportsHowto]

Anchor(Tools)

Tools

You will find some tools explained in the [:MOTU/Recipes:MOTU Recipes], also from gutsy on, you will find ubuntu-dev-tools in the archive, which contains [:UbuntuDevTools:tools for developing Ubuntu].

Anchor(NewPackages)

New Packages

The process for either requesting a new package or getting your own new package included in Ubuntu is described at ["UbuntuDevelopment/NewPackages"].

Anchor(Archive)

The Package Archive

Processes and tools to work with the Package archive are described at ["UbuntuDevelopment/PackageArchive"].

Anchor(InstallationMedia)

Installation media

Find out more in the [:UbuntuDevelopment/InstallationMedia:Installation media section].

Anchor(Resources)

Other Resources

These resources should be incorporated into new or existing sections elsewhere in this document, but are temporarily recorded here so that we remember to come back to them later:

• Ubuntu Packaging Guide: https://help.ubuntu.com/6.10/ubuntu/packagingguide/C/index.html http://doc.ubuntu.com/ubuntu/packagingguide/C/index.html

• Debian Python Policy: http://www.debian.org/doc/packaging-manuals/python-policy/

CategoryProcessBRCategoryUbuntuDevelopment