The ScriptletSnippets page indicates that packages which are converting to systemd need to include a %triggerun statement to aid in conversion. And while for some reason I remember talking about how long packages should keep this around, I don't see anywhere in the guidelines that mentions when these can be removed. The guideline sort of reads as if the trigger has to be there permanently, and some packagers appear to believe this as well.
I propose adding the following, probably to the existing admon/warning block:
Packages only need to keep this migration trigger and associated dependency for two releases, to cover the range of supported upgrades. So packages converting to systemd in F18 can drop the trigger in F21.
I don't recall a specific transition rule for systemd, but I recall a general rule of thumb related related to dropping Obsoletes/Provides, saying "Obsolete/Provides must support smooth upgrading from all active Fedoras and can be dropped afterwards.
As the maximum time span occurs during the phase when a new release "was just released" (3 active Fedora release) this would mean "a transition aid" having been introduced in F18 can be dropped in F21.
Unless I am missing something, a similar rule could be applied to systemd, also.
Yes, that's why I'm making this proposal.
This proposal passed (+1: 5, 0:0, -1:0)
(+6 if we count corsepiu's comment as a +1)
I'll write it into the guidelines.
Written up. Announcement text:
"The guidelines for migrating from sysv init scripts to systemd were clarified to state that the migration triggers only need to be kept for two releases (to cover the range of supported upgrades). For example, if the package converted to systemd unit files in F18, the migration support could be dropped in the F21. It's not mandatory that they drop them, this is just to clarify that they have the option of dropping them at that point."