Hi,

Holger Levsen <hol...@layer-acht.org> ezt írta (időpont: 2025. máj.
9., P, 12:56):
>
> On Fri, May 09, 2025 at 12:43:54PM +0200, Lucas Nussbaum wrote:
> > On 09/05/25 at 10:27 +0200, Andreas Tille wrote:
> > > > However, I have doubts about (4), since there's still so many different
> > > > workflows to use Git+Salsa.
>
> same here.

I have no doubt that migrating a package to Git is an improvement in
long term maintenance efficiency and it is not just my personal
preference.
According to https://trends.debian.net/#version-control-system >90% of
packages are maintained in git already.
I'd also enable CI by default as well ensuring that it passes thus the
original maintainer does not have to deal with broken tests should the
NMU go through.
In addition to fine grained history and CI, having a Git repository on
Salsa allows Debian Janitor to offer automated updates to the package
which is the cheapest way of keeping a package in good shape.
Eventually we could implement importing new upstream releases and
uploads from Salsa tags and maintaining a package could be as simple
as accepting MR-s and tagging a release.

> > > Which brings us back to DEP-14 as a baseline recommendation that can
> > > help reduce friction. While individual workflows vary, having some
> > > repository is a precondition for any collaboration--and DEP-14 provides a
> > > neutral, widely accepted starting point.
> > Err, the current state of things is that DEP-14 is still in CANDIDATE
> > state, and I read the last thread on this topic as unconclusive[0].
>
> that, both, plus the fact that DEP-14 does not recommend one specific
> workflow, but several.

It is sad enough that the project could not converge on a recommended
git workflow, please don't use that as an argument to hold back
improving the state of neglected packages.
DEP-14 not being officially accepted poses no practical issue for
those who really want to migrate a package to git anyway. I typically
just used gbp's default layout and lived with it or migrated to a
newer format later. A potential NMU-er should also be able to make a
good judgment call on the proposed repository format.

Migrating a neglected package to Git should be allowed for bigger
NMUs, which are offered with uploads with very long delay.

Cheers,
Balint

Reply via email to