Hi Tomas, On Fri, 13 Feb 2026 at 00:09, Tomas Volf <[email protected]> wrote:
> So, the question is, do we want some rules for the naming and versioning > of the packages (e.g., $pkg is any *released* version, and $pkg-next is > *any* version, often newer, possibly git snapshot or a release > candidate)? Or do you feel this would be governance overreach, it > should stay strictly up to the packagers and we should just document > that users who do not want release candidates should just always pin > versions of everything? As Vagrant pointed out, it seems difficult to draw a general rule. Therefore, IMHO, the best could be that each team clarifies. Well, I would not frame “stable release” vs “newer”, but why a -next variant is it required? Currently, I count ~20 packages defining a name as "foo-next" – although ~40 packages define a symbol as foo-next. Maybe each team could clarify why such gap? That said, please also note there is also ~14 packages using /pinned as their symbol. Cheers, simon
