Hi Holger, Holger Levsen <holger@layer-acht.org> writes: > On Thu, May 29, 2025 at 12:21:16AM +0200, Jonas Smedegaard wrote: >> If you suggest that using "debian/latest" should *not* be done by >> default, then it seems that requires reverting changes to DEP-14. > > yes. dep14 currently says "that uploads to unstable and experimental should > be prepared either in the debian/latest branch or respectively in the > debian/unstable and debian/experimental branches." > > I think it should (instead) recommend debian/unstable (for uploads to unstable) > (and in very brief) allow any debian/* branch layout & probably specifically > name certain common ones. > >> Personally, I don't see a problem in finalizing DEP-14 with its current >> wording, but I might miss something (more generally relevant than "let's >> just all use git-buildpackage" which I don't think is what you are >> saying here). > > my biggest problem with dep14 is that it doesnt recommend *one* layout. my > biggest problem with how I see that interpreted is that I think debian/unstable > is much better than debian/latest *as a default recommendation*. > > because IMO debian/latest is rather *not* helpful when uploads to experimental are involved. and because debian/unstable is rather very clear what this > branch is about. I am not yet a DD, but I maintain packages as a DM. Just want to provide a perspective from a "debian/latest" user, as I found using "debian/latest" easier personally. When I need to experiment something on experimental and intend to upload to unstable as soon as the experiment succeeded, using "debian/latest" provides a simple linear git timeline. If I were to use "debian/unstable", I would need to sync "debian/experimental" with "debian/unstable", do experiment there, upload; and once done, I would need merge "debian/unstable" with "debian/experimental"; and after future upload to unstable, "debian/experimental" becomes stale again and requires another merge in the future. As I don't intend to let the experimental version stay long, I think using two different branches for unstable and experimental unnecessarily complicates the process. Just my two cents. > [...] -- Regards, Xiyue Deng
Attachment:
signature.asc
Description: PGP signature