Commit 2fe8b683 authored by Andreas Tille's avatar Andreas Tille
Browse files

Hope all those occurences of alioth than can be replaced are now pointing to... 

Hope all those occurences of alioth than can be replaced are now pointing to Salsa.  Some subversion remainings are replaced as well.
parent 6dc89066

policy.xml

+7 −26
Original line number Diff line number Diff line
@@ -491,7 +491,7 @@ rm ../*_source.changes</programlisting> 
	<sect1 id="tasks">

		<title>Tasks</title>

		<para>The Debian Med <ulink url="https://blends.debian.org/blends">Debian Pure Blend</ulink> is organised by <ulink url="https://blends.debian.org/med/tasks">tasks</ulink>, that group packages around broad themes such as <ulink url="https://blends.debian.org/med/tasks/imaging">medical imaging</ulink> for instance. The tasks list programs that are already packaged in Debian as well as packages in preparation.</para>

		<para>The tasks files are not hosted in the Debian Med repositories, but in the Debian Blends repository. Nevertheless, all members of the Debian Med project on the Alioth forge have write access to the Blends subversion repository. You can easily check out its sources with the command <command>debcheckout -a debian-med</command>.</para>

		<para>The tasks files are not hosted in the Debian Med repositories, but in the Debian Blends repository. Nevertheless, all members of the Debian Med project on Salsa have write access to the Blends Git repository. You can easily check out its sources with the command <command>debcheckout -a debian-med</command>.</para>

		<para>The syntax of the tasks files is very similar to Debian control files, and described in the <ulink url="https://blends.debian.org/blends/ch08.html#edittasksfiles">Debian Blends website</ulink>.</para>

	</sect1>

	<sect1 id="policy">
@@ -615,7 +615,7 @@ Vcs-Git: https://salsa.debian.org/med-team/&lt;package&gt;.git</programlisting> 
		

		<sect2 id="debian-changelog">

			<title><filename>debian/changelog</filename></title>

			<para>Packages hosted in our Subversion repository, that have been modified but not uploaded must use <literal>UNRELEASED</literal> as a distribution name. This can be done automatically by declaring <literal><varname>DEBCHANGE_RELEASE_HEURISTIC</varname>=<replaceable>changelog</replaceable></literal> in <filename>~/.devscripts</filename> and using <command>dch</command>.</para>

			<para>Packages hosted in our Git repository, that have been modified but not uploaded must use <literal>UNRELEASED</literal> as a distribution name. This can be done automatically by declaring <literal><varname>DEBCHANGE_RELEASE_HEURISTIC</varname>=<replaceable>changelog</replaceable></literal> in <filename>~/.devscripts</filename> and using <command>dch</command>.</para>

		</sect2>

		

		<sect2 id="debian-upstream">
@@ -700,37 +700,18 @@ pristine-tar = True</programlisting> 


		<sect2 id="vcs">

			<title>Version control systems</title>

			<para>

				The Debian Med team is using Git as VCS.

			</para>

			<sect3 id="vcs-git">

				<title>Source package stored in a Git repository</title>

				<para>

					Git repositories should be stored in the <filename

					class="directory">/git/debian-med</filename> directory on Alioth and

					created with the <link

					linkend="create-git-repository-on-alioth"><command>setup-repository</command></link>

					script available there.  There, they must give write access to the

					<literal>debian-med</literal> Alioth group and all the Debian

					Developers, with appropriate Unix permissions (including SGID bit on

					directories) and ACLs.  See <filename class="directory">/git/debian-med</filename>

					itself as an example.  <command>setup-repository</command> does this

					automatically.

				</para>

				<title>Source package stored in a Git repository on Salsa</title>

				<para>

					Git repositories managed with a helper tool should announce it.  For

					instance, to show that <command>gbp buildpackage</command> is used,

					the package can contain a configuration file in

					<filename>debian/gbp.conf</filename>.

					Git repositories should be stored on <ulink url="https://salsa.debian.org/med-team/">Salsa</ulink>.

				</para>

			</sect3>

			<sect3 id="vcs-tags">

				<title>Tags</title>

				<para>

					Tags indicate the revision corresponding to uploaded packages. For

					Subversion, the version number is used, and for Git,

					<literal>debian/</literal> is added before the version number.  In the

					Subversion repository, older tags may be deleted to save space.

					Tags indicate the revision corresponding to uploaded packages.

					For a released package

					<literal>debian/</literal> is added before the package version number.

				</para>

			</sect3>

		</sect2>