ubuntu-packaging-guide-team team mailing list archive

[Daniel Holbach <daniel.holbach@xxxxxxxxxx>]

Daniel Holbach has proposed merging lp:~dholbach/ubuntu-packaging-guide/mightmightmight into lp:ubuntu-packaging-guide.

Requested reviews:
  Ubuntu Packaging Guide Team (ubuntu-packaging-guide-team)

For more details, see:
https://code.launchpad.net/~dholbach/ubuntu-packaging-guide/mightmightmight/+merge/104695

Here's the wdiff:

Open Source Development happens in a distributed world with different goals
and different areas of focus. For example there might be the case that a 
particular Upstream [-might be-] {+is+} interested in working on a new big feature while 
Ubuntu, because of the tight release schedule, [-might be-] {+is+} interested in shipping a 
solid version with just an additional bug fix. That is why we make use of 
"Distributed Development", where code is being worked on in various branches
that are merged with each other after code reviews and sufficient discussion.

-- 
https://code.launchpad.net/~dholbach/ubuntu-packaging-guide/mightmightmight/+merge/104695
Your team Ubuntu Packaging Guide Team is requested to review the proposed merge of lp:~dholbach/ubuntu-packaging-guide/mightmightmight into lp:ubuntu-packaging-guide.

=== modified file 'ubuntu-packaging-guide/introduction-to-ubuntu-development.rst'
--- ubuntu-packaging-guide/introduction-to-ubuntu-development.rst	2012-02-29 10:05:20 +0000
+++ ubuntu-packaging-guide/introduction-to-ubuntu-development.rst	2012-05-04 07:53:19 +0000
@@ -87,9 +87,9 @@
 
 Open Source Development happens in a distributed world with different goals
 and different areas of focus. For example there might be the case that a 
-particular Upstream might be interested in working on a new big feature while
-Ubuntu, because of the tight release schedule, might be interested in shipping 
-a solid version with just an additional bug fix. That is why we make use of 
+particular Upstream is interested in working on a new big feature while 
+Ubuntu, because of the tight release schedule, is interested in shipping a 
+solid version with just an additional bug fix. That is why we make use of 
 "Distributed Development", where code is being worked on in various branches
 that are merged with each other after code reviews and sufficient discussion.