From 2f23142b4d10fdf431de8a48137f26c6e5d995d6 Mon Sep 17 00:00:00 2001 From: Otto Liljalaakso Date: Sep 29 2022 21:25:46 +0000 Subject: Recommend using side tags in Package Maintenance Guide Package Maintenance Guide's section Requesting special dist tags recommended filing a release engineering issue to create a "special repository" for the use case that is nowadays handled with a side tag created by the packages as self service. Since side tags are already covered in the Package Update Guide, the Maintenance Guide's separate instructions are replaced with a link to the Update Guide. --- diff --git a/modules/ROOT/pages/Package_Maintenance_Guide.adoc b/modules/ROOT/pages/Package_Maintenance_Guide.adoc index 45faf70..307c297 100644 --- a/modules/ROOT/pages/Package_Maintenance_Guide.adoc +++ b/modules/ROOT/pages/Package_Maintenance_Guide.adoc @@ -406,22 +406,14 @@ git commit .... [#requesting_special_dist_tags] -== Requesting special dist tags +== Multi-package updates When a change to a package affects a large number of dependencies (e.g. all perl, python, ruby or ghc packages), requiring them to be rebuilt, -it may be better to initially do the builds in a special repository, +it may be better to initially do the builds in a _side tag_, so that there is less disruption in Rawhide. - -If you think you have an update that falls under this case -you can request a special dist tag -by filing a https://pagure.io/releng/new_issue[release engineering ticket]. -Someone from https://docs.pagure.org/releng/[release engineering] will likely want -to discuss your needs -to make sure this is really an appropriate case -(it's OK ask if you aren't sure) -and that you get what you need. +See xref:Package_Update_Guide.adoc#multiple_packages[Package Update Guide, section Multi-package updates] for details. [#using_fedpkg_anonymously] == Using fedpkg anonymously