On 25 October 2017 at 16:16, Kai Engert <kaie@xxxxxxx> wrote: > On 25.10.2017 15:22, James Hogarth wrote: >> There's always process if something is high enough level to be >> considered a "Change" >> >> Please follow the appropriate process to have this included as a >> system level change for F28. > > Ok. The change was previously accepted for Fedora 27. > > I've edited and updated the previous trackers: > - > https://fedoraproject.org/wiki/Changes/NSSDefaultFileFormatSql#Current_status > - https://bugzilla.redhat.com/show_bug.cgi?id=1474771 > - https://pagure.io/releng/issue/6883 > > Will this be sufficient to restart the change acceptance process for > Fedora 28? > Although I'm not on FESCo my advice here is to treat it as a fresh change and for the large part ignore the missed target of F27. You're fortunate that Change is already written up so you're spared redoing that effort and also that the contingency is known, and in this case tested. If steps are skipped then it risks other Changes in future adopting the "we tried it for N-1 and it was approved in N-1 so we're good" causing problems... and besides risks to be aware of will change from release to release. If we follow process each time, whether it was a missed target previously or not, we ensure that there are no slip ups with missing documentation or knock on effects that have not been considered. In general if you have to ask the question "Will this be sufficient to restart the change acceptance process for Fedora Next?" then realistically the only suitable response is "check with FESCo, which you'd have to do with any Change anyway". _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
