Hi,
Am 24.01.25 um 02:06 schrieb Otto Kekäläinen:
I would be curious to hear why people are *not* adopting 'debian/latest'?
Why does the majority of Debian packages still use 'master' or
'debian/master' branch as the main development branch?
Is it simply because git-buildpackage does not to default to 'debian/latest'?
I am maintaining a package which does only have debian/ in git, so gbp stuff
does not really apply, but still.
People also asked about this for that one. And got confused that master is sid.
So I am chiming it since rules which do not make real sense impose problems.
What should debian/latest be? The latest upstream (pre-)release? Aka what is in
experimental? Or not even there,
just preparing stuff for experimental?
That would confuse people and waste peoples time.
People look up debian/latest and see stuff not relevant for sid where they ae
working on/for. Especially on freezes where stuff still happens for
experimental.
Or even worse, as follows:
"Latest stuff"? That would in my case be a version which will only be released
in August and has not even have a pre-release yet. The alpha
will be in May only.
Because I usually do try to follow and do stuff well before so I am ready when it gets
"hot".
(Ideally even uploading on the day of the release itself.)
And no, I am not doing "let's wait for X, then adapt, missing stuff here and there
and waiting for some time to sort it out" thingy some maintainers seem to do.
debian/latest is bad here.
I use master for sid and anything else is branches.
Regards,
Rene
