[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Merge behaviour for team packages



Samuel Henrique <samueloph@debian.org> writes:

>> Btw, tag2upload doesn't need any hooks any more.  I've uploaded some
>> pkg-security packages and it works fine.  I suggest everyone consider
>> using 'git-debpush' to release and upload packages.
>
> I've also heard good things about debusine, I'd like to also give that a go
> sometime.

Me too, but they seem to be for different use-cases.  Tag2upload uploads
things into the archive, Debusine build packages.  I never had a big
problem getting packages built, Salsa CI does it nicely for me, so I'm
waiting for some use-case for Debusine.  Doing reverse builds may be
one, but I just noticed that Salsa CI added this functionality.  So I'm
not really sure what I would use Debusine for really.

>> Btw^2, my perception is that DEP14 debian/latest is more common than
>> debian/unstable, but my view is limited so this may be biased.  In case
>> you want to consider another data point before recommending
>> debian/unstable as a team policy.
>
> I don't like debian/latest as opposed to debian/unstable because it
> gets confusing when someone wants to upload packages to experimental
> (debian/latest + debian/experimental), but it's not the end of the
> world, what matters the most is consistency IMO.

Interesting -- in my head I have a rule like this:

1) Use debian/latest whenever package uploads are mostly linear in that
N goes to unstable, N+1, N+2 goes to experimental and N+3 goes to
unstable, and that the goal of experimental uploads is to get something
worthy of unstable upload.  (This is very much what I'm doing for the
'nsd' package right now, but I now realize that I use
debian/experimental there...)

2) Use debian/sid (or debian/unstable) AND debian/experimental (or I
suppose debian/rc-buggy which I've seen some use) concurrently when
development happen in two different branches over a long period of time,
and when the goal is to actually be able to ship two different upstream
versions concurrently.

Thus one should never really use debian/latest + debian/experimental at
the same time, except for exceptional cases. (And here I realize I just
made this mistake for the 'nsd' package..)

However the more I work with this I realize it is all just subjective
and up to personal preference, which is very much biased towards what
you've been exposed to.

HOWEVER what I've seen is also that debian/sid is more common than
debian/unstable, but I don't have statistics to back that up.

/Simon

Attachment: signature.asc
Description: PGP signature


Reply to: