On Mon, Jul 01, 2024 at 01:18:58PM +0900, Simon Richter wrote: > Hi, > > On 7/1/24 04:55, Aigars Mahinovs wrote: > > > - if the NMU author has access to the main git repo of the package on > > Salsa they can make a commit and tag there (normal team-like > > maintenance) > > If we create a method with a low technical barrier for NMUing, we also need > to have a discussion about procedural expectations for that at some point. > > Like, if someone makes an NMU that solves a problem, but creates maintenance > issues down the line, is it acceptable to back that out immediately? > > In a pure git workflow, it is understood that if you are not usually > involved with the project, you'd send a pull request rather than merge > directly, but since we're all somehow "involved" with Debian, I'd expect the > barrier for just committing changes to other people's packages to be > somewhat lower -- which may be good or bad. I'm not sure I understand these questions correctly. The technical barrier for NMUing is already low, and you (the maintainer) are already expected to keep the NMU changes, the NMU changelog entry (even if you revert the changes) and, consequently, git commits (likely created by you from the NMU upload) that add those. -- WBR, wRAR
Attachment:
signature.asc
Description: PGP signature