-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Thu, 2018-03-08 at 13:00 -0500, Randy Barlow wrote: > Greetings fellow Fedorans! > > I would like to kick off a general discussion about how we might gate > packages in Rawhide. I think it would be nice to get something in > place > for the Fedora 29 timeframe. > > As one of the Bodhi contributors, I am inclined to suggest that we > could > use Bodhi on Rawhide, similar to how we use it for our > stable/branched > releases, with more relaxed rules (perhaps 1 day in testing or > something > simple). > > It may be possible to automate the process a bit to make it less > heavy > for developers, though there is some complication for multi-package > updates (more on that in a bit). For simple package updates, we may > be > able to detect new commits on dist-git, and react to those by > automatically starting a Koji build, and automatically filing a Bodhi > update when that build is complete. I think that would be pretty > nice, > and pingou created a PoC[0] to do this about a year ago. > > Multi-package updates won't be so easy though. It's not uncommon for > us > to need to update packages together, and the above workflow would be > problematic since it would result in updates with single packages in > them rather than updates with multiple packages. Of course, buildroot > overrides would be a problem too, since multi-package updates often > depend on each other at build time too. > > We could create some way for packagers to indicate that a commit (or > possibly even a whole repo) is not intended to be > "autobuilt/updated". > If the packager indicates this then their builds would go into a > rawhide-pending (similar to what we do for f27 today). Once they have > all their builds (and buildroot overrides) the way they want them, > they > can create the update. > > Another idea that was tossed around in some chats I had with people > about this involved a system for packagers to use to create Koji side > tags. Bodhi manages BuildRoot Overrides today (with expirations), so > perhaps Bodhi could be expanded to also manage Koji side tags (also > with > expirations). I can't remember all the details about this approach or > why it was suggested over the former approach, but I wanted to list > it > to invite others to chew on it and see if it could work. > > If you have other suggestions on how we might gate packages in > Rawhide > that are wildly different than the above, please feel free to share! I would not mind this, but making buildroot overrides is something what makes me to not update N-1 release.. Especially when I need to build 15-20 packages which have some dependency loops. - -- - -Igor Gnatenko -----BEGIN PGP SIGNATURE----- iQIyBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlqhuGoACgkQaVcUvRu8 X0yNig/4nryfRqiDy6hTU2UgDxznTt/kg4/MXcqo02aNzcMOPf5Iel7XN3rs+Hqq r8oIzzWE/1rldMdF6s/G/9vY0vpcRox9jZylMumevH59T8w6nTMioPqEcAKM3s2w 0SF6D+Mcj/US0pKaQhp6vcmOfHbXBfuBIl6XROW2rBKhCtjQhkU8bhBV9ku4qLxF 1rkk0yN06t4ULWeJmnAyBKYiU+fGGlixJCP6xeghrH3Vb5jsDC3weLSOm177V3zL WCO4x7jtca/DbtW/CbHnJeIM7DzaAIL6FbfYQDBK9Z2xmEyH6JdnMrMdI4ItWvWM KZQVEyWlx2cM0+dKJLvwgjDpMwHS6xsujxQCw7gaTTgDgsMgOz8dBxjgG/rQP1mK D7sE2sKVVqwWOTCqOx9U2revpqLv2lD4Hq0Ecrklpph9SPs67YhdnJnWrhr1L8bz xAd+j+JADbEtgwolWFDhrYS4rmmSm4mNTSAD0+HOCmkjHW0IYsXR/QRSsCzK/OJ0 gJHB3d4eCzk0AWILW12r8fyoJ6U344lNABk3irPQHparAaPxVsREIg35yAROWQP+ dmGefvsYUiR1w6+wUyTbKhttQId0gq8IH7N85yypVFQlHEqTxoUgu8RCOxga4AVA FIv8ZsdPgfz3MYRvrynqZr+/F2RQ9avcZ8hYe1Ae5nlPaANWFw== =1LVE -----END PGP SIGNATURE----- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
