[Debian-med-packaging] Our SVN and Git tips for backports
Afif Elghraoui
afif at ghraoui.name
Sun Aug 16 17:07:14 UTC 2015
Hi, all,
On الأحد 16 آب 2015 02:43, Andreas Tille wrote:
> 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
No problem. That statement about subversion branches was there before
and I just added onto it.
> 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.
>
That would be nice.
>> 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).
>
I agree as well--I just wasn't aware. Branch renaming isn't a problem.
Thanks and regards
Afif
--
Afif Elghraoui | عفيف الغراوي
http://afif.ghraoui.name
More information about the Debian-med-packaging
mailing list