[Debian-med-packaging] Our SVN and Git tips for backports (Re: [med-svn] r19939 - trunk/community/website/docs)

[Charles Plessy]

Le Sat, Aug 15, 2015 at 04:05:09AM +0000, Afif Elghraoui a écrit :
>  			<title>Backports</title>
>  			<para>
> -				Debian offers <ulink url="http://backports.debian.org">backports</ulink> to its stable version.  Backports of Debian Med packages should be kept as branches in our <link linkend="svn-repository-structure">Subversion</link> or <link linkend="git-repository-structures">Git</link> repositories.
> +			  Debian offers <ulink url="http://backports.debian.org">backports</ulink> to provide
> +			  up-to-date software for users of the official stable releases. Backports of Debian Med packages
> +			  should be kept as branches in our <link linkend="svn-repository-structure">Subversion</link> or
> +			  <link linkend="git-repository-structures">Git</link> repositories. In Git, the branch should be
> +			  named using the release code names. As an example, the backports branch for Debian 8 ("jessie")
> +			  should be named <literal>debian/jessie</literal>.

Hi Afif,

thanks for the update.  I have two small comments.

For packages managed in Subversion, it is widely tolerated here to not use a
branch for the backports (even, to not commit anything), because it does not
fit well with our usual workflow, where only the "trunk" branch is checked out.

For Git, I think that the debian/jessie branch should be reserved for stable
update; for backports debian/jessie-backports seems more natural to me.  I
think that this is also more in line with DEP 14.

Cheers,

Charles

-- 
Charles Plessy
Debian Med packaging team,
http://www.debian.org/devel/debian-med
Tsurumi, Kanagawa, Japan