/usr/share/doc/ubuntu-packaging-guide-html-de/udd-sponsorship.html is in ubuntu-packaging-guide-html-de 0.3.7.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 | <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>6. Sponsoring und Nachprüfung finden — Ubuntu Packaging Guide</title>
<link rel="shortcut icon" href="./_static/images/favicon.ico" type="image/x-icon" />
<link rel="stylesheet" href="./_static/reset.css" type="text/css" />
<link rel="stylesheet" href="./_static/960.css" type="text/css" />
<link rel="stylesheet" href="./_static/base.css" type="text/css" />
<link rel="stylesheet" href="./_static/home.css" type="text/css" />
<link rel="stylesheet" href="./_static/pygments.css" type="text/css" />
<link rel="stylesheet" href="./_static/guide.css" type="text/css" />
<script type="text/javascript">
var DOCUMENTATION_OPTIONS = {
URL_ROOT: '../',
VERSION: '0.3.7',
COLLAPSE_INDEX: false,
FILE_SUFFIX: '.html',
HAS_SOURCE: true
};
</script>
<script type="text/javascript" src="./_static/jquery.js"></script>
<script type="text/javascript" src="./_static/underscore.js"></script>
<script type="text/javascript" src="./_static/doctools.js"></script>
<script type="text/javascript" src="./_static/translations.js"></script>
<script type="text/javascript" src="./_static/main.js"></script>
<link rel="top" title="Ubuntu Packaging Guide" href="./index.html" />
<link rel="next" title="7. Ein Paket hochladen" href="udd-uploading.html" />
<link rel="prev" title="5. An einem Paket arbeiten" href="udd-working.html" />
</head>
<body class="home">
<a name="top"></a>
<div class="header-navigation">
<div>
<nav role="navigation">
<ul>
<li class="page_item current_page_item"><a title="Inhalt" href="index.html">Inhalt</a>
<li>
<form id="form-search" method="get" action="search.html">
<fieldset>
<input id="input-search" type="text" name="q" value="Search" />
</fieldset>
</form>
</li>
</ul>
</nav>
<a class="logo-ubuntu" href="http://packaging.ubuntu.com/">
<img src="./_static/images/logo-ubuntu.png" width="119" height="27" alt="Ubuntu logo" />
</a>
<a href="http://packaging.ubuntu.com/"><h2>Packaging Guide</h2></a>
</div>
</div>
<div class="header-content">
<div class="clearfix">
<div class="header-navigation-secondary">
<div>
<nav role="navigation">
<ul class="clearfix">
<li class="page_item"><a style="margin-right: 10px"
href="udd-uploading.html" title="7. Ein Paket hochladen"
accesskey="N">weiter</a></li>
<li class="page_item"><a
href="udd-working.html" title="5. An einem Paket arbeiten"
accesskey="P">zurück</a></li>
<li class="page_item"><a class="sub-nav-item" href="index.html">Ubuntu Packaging Guide »</a></li>
</ul>
</nav>
</div>
</div>
</div>
</div>
<div id="content" class="body container_12">
<div class="grid_12">
<!--<section id="main-section">-->
<div class="grid_9 alpha">
<div class="section" id="seeking-review-and-sponsorship">
<h1>6. Sponsoring und Nachprüfung finden<a class="headerlink" href="#seeking-review-and-sponsorship" title="Permalink zu dieser Überschrift">¶</a></h1>
<p>One of the biggest advantages to using the UDD workflow is to improve quality
by seeking review of changes by your peers. This is true whether or not you
have upload rights yourself. Of course, if you don’t have upload rights, you
will need to seek sponsorship.</p>
<p>Once you are happy with your fix, and have a branch ready to go, the following
steps can be used to publish your branch on Launchpad, link it to the bug
issue, and create a <em>merge proposal</em> for others to review, and sponsors to
upload.</p>
<div class="section" id="pushing-to-launchpad">
<span id="merge-proposal"></span><h2>6.1. Zu Launchpad hochladen<a class="headerlink" href="#pushing-to-launchpad" title="Permalink zu dieser Überschrift">¶</a></h2>
<p>We previously showed you how to <a class="reference internal" href="udd-working.html#link-via-changelog"><em>associate your branch to the bug</em></a> using <tt class="docutils literal"><span class="pre">dch</span></tt> and <tt class="docutils literal"><span class="pre">bzr</span> <span class="pre">commit</span></tt>. However, the branch
and bug don’t actually get linked until you push the branch to Launchpad.</p>
<p>It is not critical to have a link to a bug for every change you make,
but if you are fixing reported bugs then linking to them will be useful.</p>
<p>Die allgemeine Form der URL, zu der Du Deinen Branch hochlädst ist:</p>
<div class="highlight-python"><div class="highlight"><pre>lp:~<user-id>/ubuntu/<distroseries>/<package>/<branch-name>
</pre></div>
</div>
<p>For example, to push your fix for bug 12345 in the Tomboy package for Trusty,
you’d use:</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr push lp:~subgenius/ubuntu/trusty/tomboy/bug-12345
</pre></div>
</div>
<p>Die letzte Komponente des Pfades ist frei wählbar, am besten entscheidest Du Dich für etwas dass Deine Änderung am treffendsten beschreibt.</p>
<p>However, this usually isn’t enough to get Ubuntu developers to review and
sponsor your change. You should next submit a <em>merge proposal</em>.</p>
<p>Um dies zu tun, öffne den Bug-Report in Deinem Browser, z.B.:</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr lp-open
</pre></div>
</div>
<p>Sollte dies fehlschlagen, dann benutze:</p>
<div class="highlight-python"><div class="highlight"><pre>$ xdg-open https://code.launchpad.net/~subgenius/ubuntu/trusty/tomboy/bug-12345
</pre></div>
</div>
<p>where most of the URL matches what you used for <cite>bzr push</cite>. On this page,
you’ll see a link that says <em>Propose for merging into another branch</em>. Type
in an explanation of your change in the <em>Initial Comment</em> box. Lastly, click
<em>Propose Merge</em> to complete the process.</p>
<p>Merge proposals to package source branches will automatically subscribe the
<cite>~ubuntu-branches</cite> team, which should be enough to reach an Ubuntu developer
who can review and sponsor your package change.</p>
</div>
<div class="section" id="generating-a-debdiff">
<h2>6.2. Ein Debdiff erzeugen<a class="headerlink" href="#generating-a-debdiff" title="Permalink zu dieser Überschrift">¶</a></h2>
<p>As noted above, some sponsors still prefer reviewing a <em>debdiff</em> attached to
bug reports instead of a merge proposal. If you’re requested to include a
debdiff, you can generate one like this (from inside your <cite>bug-12345</cite>
branch):</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr diff -rbranch:../tomboy.dev
</pre></div>
</div>
<p>Ein weiterer Weg dies zu tun ist den Merge-Vorschlag im Browser zu öffnen und das Diff herunterzuladen.</p>
<p>You should ensure that diff has the changes you expect, no more and no less.
Name the diff appropriately, e.g. <tt class="docutils literal"><span class="pre">foobar-12345.debdiff</span></tt> and attach it to
the bug report.</p>
</div>
<div class="section" id="dealing-with-feedback-from-sponsors">
<h2>6.3. Umgang mit Feedback der Sponsoren<a class="headerlink" href="#dealing-with-feedback-from-sponsors" title="Permalink zu dieser Überschrift">¶</a></h2>
<p>If a sponsor reviews your branch and asks you to change something, you can do
this fairly easily. Simply go to the branch that you were working in before,
make the changes requested, and then commit:</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr commit
</pre></div>
</div>
<p>Wenn Du Deinen Branch nach Launchpad hochlädst, wird sich Bazaar merken wohin und der Branch in Launchpad wird aktualisiert mit Deinen letzten Commits. Alles was Du tun musst, ist:</p>
<div class="highlight-python"><div class="highlight"><pre>$ bzr push
</pre></div>
</div>
<p>You can then reply to the merge proposal review email explaining what you
changed, and asking for re-review, or you can reply on the merge proposal page
in Launchpad.</p>
<p>Note that if you are sponsored via a debdiff attached to a bug report you need
to manually update by generating a new diff and attaching that to the bug
report.</p>
</div>
<div class="section" id="expectations">
<h2>6.4. Erwartungen<a class="headerlink" href="#expectations" title="Permalink zu dieser Überschrift">¶</a></h2>
<p>The Ubuntu developers have set up a schedule of “patch pilots”, who regularly
review the sponsoring queue and give feedback on branches and patches. Even
though this measure has been put in place it might still take several days
until you hear back. This depends on how busy everybody is, if the development
release is currently frozen, or other factors.</p>
<p>Wenn Du eine Weile nichts mehr gehört hast, schaue einfach in <cite>#ubuntu-devel</cite> auf <cite>irc.freenode.net</cite> ob Dir jemand dort helfen kann.</p>
<p>Weitere Informationen über den allgemeinen Prozess für Sponsoring, sind auf <a class="reference external" href="https://wiki.ubuntu.com/SponsorshipProcess">https://wiki.ubuntu.com/SponsorshipProcess</a> verfügbar.</p>
</div>
</div>
<div class="divide"></div>
</div>
<div id="sidebar" class="grid_3 omega">
<div class="container-tweet">
<h3>Inhalt</h3>
<div class="toc">
<ul>
<li><a class="reference internal" href="#">6. Sponsoring und Nachprüfung finden</a><ul>
<li><a class="reference internal" href="#pushing-to-launchpad">6.1. Zu Launchpad hochladen</a></li>
<li><a class="reference internal" href="#generating-a-debdiff">6.2. Ein Debdiff erzeugen</a></li>
<li><a class="reference internal" href="#dealing-with-feedback-from-sponsors">6.3. Umgang mit Feedback der Sponsoren</a></li>
<li><a class="reference internal" href="#expectations">6.4. Erwartungen</a></li>
</ul>
</li>
</ul>
</div>
<div class="browse-guide">
<h3>Browse The Guide:</h3>
<ul>
<li class="prev">
<a href="udd-working.html"
title="Vorheriges Thema: 5. An einem Paket arbeiten">Go Previous</a>
</li>
<li class="center">
<a title="Back to Index" href="index.html">Index Guide</a>
</li>
<li class="next">
<a href="udd-uploading.html"
title="Nächstes Thema: 7. Ein Paket hochladen">Go Next</a>
</li>
</ul>
<span>Diese Seite:</span> <a href="./_sources/udd-sponsorship.txt"
rel="nofollow">Quelltext anzeigen</a>
</div>
</div>
<div id="back_top"><a href="#top">Back to Top</a></div>
</div>
<!--</section>-->
</div>
</div>
<div class="shadow"></div>
<footer>
<div>
Version: 0.3.7.
<a href="https://bugs.launchpad.net/ubuntu-packaging-guide">Report bugs</a> or
<a href="https://code.launchpad.net/~ubuntu-packaging-guide-team/ubuntu-packaging-guide/trunk">grab the source code</a> from Launchpad.
Mit <a href="http://sphinx-doc.org/">Sphinx</a> 1.2.3 erstellt.
<br />
© Copyright 2010-2015, Ubuntu Developers, Creative Commons Attribution-ShareAlike 3.0.
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">
Creative Commons Attribution-ShareAlike 3.0 Unported License</a>.
<a rel="license" href="http://creativecommons.org/licenses/by-sa/3.0/">
<img alt="Creative Commons License" style="border-width:0"
src="./_static/images/cc-by-sa.png" /></a>
<br />
<a href="http://people.ubuntu.com/~mitya57/ubuntu-packaging-guide-readme.html#translating">Help translate</a> or
<a href="./_static/translators.html">view the list of translators</a>.
</div>
</footer>
</body>
</html>
|