← Back to branch summary

~josephjamesmills/ubuntu-packaging-guide/fixed-bug975026

« back to all changes in this revision

Viewing changes to ubuntu-packaging-guide/introduction-to-ubuntu-development.rst

  • Committer: Daniel Holbach
  • Date: 2012-03-20 22:02:49 UTC
  • mfrom: (78.2.26 upg-i18n)
  • Revision ID: daniel.holbach@canonical.com-20120320220249-pljexws010dw6cbi
merged lp:~andrewsomething/ubuntu-packaging-guide/i18n

Show diffs side-by-side

added added

removed removed

Lines of Context:
ubuntu-packaging-guide/introduction-to-ubuntu-development.rst
34
34
candidate release is made and if it does not contain any serious problems, it 
35
35
becomes the final release.
36
36
 
37
 
.. image:: images/cycle-items.png
 
37
.. image:: ../images/cycle-items.png
38
38
 
39
39
Thousands of source packages, billions of lines of code, hundreds of
40
40
contributors require a lot of communication and planning to maintain
93
93
"Distributed Development", where code is being worked on in various branches
94
94
that are merged with each other after code reviews and sufficient discussion.
95
95
 
96
 
.. image:: images/cycle-branching.png
 
96
.. image:: ../images/cycle-branching.png
97
97
 
98
98
In the example mentioned above it would make sense to ship Ubuntu with the 
99
99
existing version of the project, add the bugfix, get it into Upstream for 
107
107
Ubuntu development release. A developer with upload rights will review it for 
108
108
you and then get it integrated into Ubuntu.
109
109
 
110
 
.. image:: images/cycle-process.png
 
110
.. image:: ../images/cycle-process.png
111
111
 
112
112
When trying to find a solution it is usually a good idea to check with 
113
113
Upstream and see if the problem (or a possible solution) is known already