RE: Needing branches for releases ?
[AMD Official Use Only - AMD Internal Distribution Only]
I would prefer a standard as well, thanks for pointing this out.
I am interested in expanding my POC to cover more of the stack and have some branching to try out some release and/or ci workflows.
It is very challenging to have a very fast upstream and a lot of packages. Patch releases happen about every 4-6 weeks. This takes us in fedora about 2 weeks but this leans on a lot of fedora processes that I am not sure have a Debian equivalent. If there is a some better/different way folks aways wanted to try out, I would be willing to give those a try otherwise I'll do the best I can to reduce the manual overhead per package.
Tom
-----Original Message-----
From: Christian Kastner <ckk@debian.org>
Sent: Sunday, July 6, 2025 11:10 AM
To: debian-ai@lists.debian.org
Subject: Re: Needing branches for releases ?
Hi Tom,
there is a lot of useful info in your mail to look into, below I'm just quickly addressing the question you asked.
On 2025-07-06 17:14, Rix, Tom wrote:
> Some topics for our meet up this week.
>
> I hope I am wrong, but there don't seem to be any branches so how are
> releases supported ?
Not in the current layout, but that's because it's just the default gbp layout that we've continued to use because it's easy.
If we switch to DEP-14 layout [1], then you'd have releases at
debian/bookworm
debian/trixie
debian/experimental
debian/latest (used to be debian/master)
ubuntu/puffin
...
We could also continue with the current layout and just add
bookworm
trixie
puffin
without the vendor prefix, to the same effect, but I personally find
DEP-14 cleaner. Also, standardization is a plus.
> Without the branches basic maintenance on the releases, like CVE or
bug fixes cannot be done.
Correct.
Best,
Christian
[1]: https://dep-team.pages.debian.net/deps/dep14/
Reply to: