On Wed, Nov 23, 2022 at 2:52 PM Kevin Fenzi <ke...@scrye.com> wrote: > > Greetings everyone. > > So, we used to have a release requirement that we package up and release > along side the release a spin-kickstarts rpm package with the current > kickstarts used for that release. > > This resulted in a bunch of last minute scrambling and blockers, and > even then, we often pushed fixes after release and people would get the > out of date one in the package and get confused. > > So, we changed that requirement, but then since there was no > requirement, we haven't really been updating the rpm much. > (see https://bugzilla.redhat.com/show_bug.cgi?id=2144207 ) > > I'd like to just retire the rpm package and point folks to the git repo. > I think this will get people up to date versions of things, > and avoid pointlessly updating a package. > > Anyone have any arguments to save the rpm version? > Or shall I just retire it/update docs? >
Is there a reason we couldn't just automatically update the package once we're in freeze so that it has what we're shipping? By the time we're down to the wire for final freeze, we're not changing the kickstarts that often. -- 真実はいつも一つ！/ Always, there's only one truth! _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
