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

Andreas Tille andreas at an3as.eu
Sun Aug 16 09:43:24 UTC 2015


On Sun, Aug 16, 2015 at 06:16:40PM +0900, Charles Plessy wrote:
> 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.

+1
We even might consider moving those packages to Git that deserve a backport.
I do not think that Afif will consider crafting the automatic backporting
stuff for more than one VCS.
 
> 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.

We should by all means try to be as close as possible to DEP 14.  Afif,
if you agree as well we have three votes for this and you can change
this in Policy.  I guess there is some easy way to rename branches in
Git (since I had used debian/jessie in some cases).

Kind regards

      Andreas.

-- 
http://fam-tille.de



More information about the Debian-med-packaging mailing list