Il 24/01/2025 14:25, Tobias Frost ha scritto:
Hi, for years on some packages every new major version I did the uploads on experimental first, in addition to the cases of feature freeze, master was the default branch and I did it on experimental branch changing d/gbp.conf, d/salsa-ci.yml and d/control, recently I switched to debian/latest and I'm keeping it there whether you upload to experimental or sid and I think that doing debian/unstable (or debian/sid) less frequently only if you have the latest in experimental but need some urgent fixes in unstable greatly reduces the need to change branches (with a few more operations only for where you upload).Am Fri, Jan 24, 2025 at 09:16:50AM +0300 schrieb Michael Tokarev:24.01.2025 04:06, Otto Kekäläinen wrote:3. "latest" is a misnomer (unlike "main" or "master"). For example, I often use "experimental" branch which is more recent than "master", yet the main development is happening in "master".Same here. I think "latest" is a bad choice, as it is ambigious in some situations: For example, is my experiment(al) package* latest or is the one target for the next stable latest? For me, it is much clearer to say e.g "debian/sid" or "debian/experimental" to express what I want. * (noting that experiments might not end up in sid, those changes might not * even have a business in the latest branch.)
So even if it may seem vague it depends on how you choose to do things and in many cases you could save time if you keep a generic branch as default rather than one tied to unstable or experimental (which requires more operations even when not necessary to maintain consistency)
There is also another thing to consider, if you keep a generic one as default it always points to the latest version, while a specific one might not be the latest version and if the contributors do not check well the branches they could risk wasting time (and maybe also the reviewers) doing work that does not include work in progress on more recent branch or that conflicts with it
There were cases when git wont let me use debian/foo "branch subdir" since it clashed with other objects in the git repository, but I don't remember what it was.(Maybe that you cannot have <$branch> and <$branch>/something)Thanks, /mjt
OpenPGP_signature.asc
Description: OpenPGP digital signature
