[website] 01/10: Add custom TOC for packaging walkthough subsections.

Sebastiaan Couwenberg sebastic at moszumanska.debian.org
Fri Apr 24 19:34:21 UTC 2015


This is an automated email from the git hooks/post-receive script.

sebastic pushed a commit to branch master
in repository website.

commit c76b2ceeab75a51a9608e52cf5ac7c97e89d1ae8
Author: Bas Couwenberg <sebastic at xs4all.nl>
Date:   Fri Apr 24 15:25:24 2015 +0200

    Add custom TOC for packaging walkthough subsections.
---
 policy.xml | 70 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
 1 file changed, 69 insertions(+), 1 deletion(-)

diff --git a/policy.xml b/policy.xml
index 79f0f63..c0d4d19 100644
--- a/policy.xml
+++ b/policy.xml
@@ -792,8 +792,76 @@ pkg-grass/
       <sect3 id="git-walkthrough">
         <title>Packaging walkthrough</title>
         <para>
-          ...
+          The packaging walkthough is split into the following subsections:
         </para>
+        <itemizedlist>
+          <listitem>
+            <para>
+              <link linkend="git-pbuilder">Setup the build environment</link>
+              <itemizedlist>
+                <listitem>
+                  <para>
+                    <link linkend="git-pbuilder-hooks">Configure lintian pbuilder hook</link>
+                  </para>
+                </listitem>
+              </itemizedlist>
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <link linkend="git-new-package">Starting a new package</link>
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <link linkend="git-existing-package">Working with existing packages</link>
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <link linkend="git-new-upstream">Upgrading to a new upstream release</link>
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <link linkend="git-build-package">Building the package</link>
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <link linkend="git-push">Pushing to git.debian.org</link>
+              <itemizedlist>
+                <listitem>
+                  <para>
+                    <link linkend="git-repository-on-alioth">Create a Git repository on Alioth</link>
+                  </para>
+                </listitem>
+                <listitem>
+                  <para>
+                    <link linkend="git-alioth-remote">Configure a Git remote for the repository</link>
+                  </para>
+                </listitem>
+                <listitem>
+                  <para>
+                    <link linkend="push-package-to-alioth">Push the package</link>
+                  </para>
+                </listitem>
+              </itemizedlist>
+            </para>
+          </listitem>
+          <listitem>
+            <para>
+              <link linkend="git-release-upload">Uploading a new package release</link>
+              <itemizedlist>
+                <listitem>
+                  <para>
+                    <link linkend="git-tag-release">Tag a release</link>
+                  </para>
+                </listitem>
+              </itemizedlist>
+            </para>
+          </listitem>
+        </itemizedlist>
         <sect4 id="git-pbuilder">
           <title>Setup the build environment</title>
           <para>

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-grass/website.git



More information about the Pkg-grass-devel mailing list