Sharlatan Hellseher <[email protected]> writes: > Hi Guix, > > Hope everyone is well ! > > This topic occupied me for a while. > I know there is some documented practice s, but I feel we missing some > formalism and templates when the deprecation issue is open. > > Would it be any interest among community to have something like > this as proper GCD? > > - an agreed template for package deprecation issue > > Title: Remove <package-name>@<version>: Breaf reasoning. > Body: > More detailed reasoning > Guix git history of the package updates > Any open upstream issues > Any alternative if there is any > List of other channels informed about depression > Attached full build log > > - agreed list of the channels to be informed (guix-science, guix-past, ...) > > - document when to add : -next, -bootstrap, -minimal, or apply graft > and when/how to remove them > > I hope to boost some coordination between related channel, > I also may be useful to attract some attention when help to fix > is wanted. > > Thanks, > Oleg > > VCS: https://github.incerto.xyz/; https://git.sr.ht/~hellseher/ > GPG: 9847 81DE 689C 21C2 6418 0867 76D7 27BF F62C D2B5 > > … наш разум - превосходная объяснительная машина которая способна найти > смысл почти в чем угодно, истолковать любой феномен, но совершенно не в > состоянии принять мысль о непредсказуемости.
Hi Oleg, > Would it be any interest among community to have something like > this as proper GCD? I think this is a great idea, I also think that our deprecation mechanisms need to be upgraded. One request: policy for moving packages between modules. > - agreed list of the channels to be informed (guix-science, guix-past, > ...) Maybe make a mailing list that channels can subscribe to just for deprecation warnings? Or in theory, if the deprecation macros are always used for a sufficient time there should be no need for that. Good day, Noé
signature.asc
Description: PGP signature
