From 19b6dd8e07dbca4662afd7461bf76d6e693b13c6 Mon Sep 17 00:00:00 2001 From: Ben Cotton Date: Jan 29 2020 13:22:22 +0000 Subject: Clean up some formatting on lists (and un-list things that are actually paragraphs) --- diff --git a/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc b/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc index 8feb723..faef94f 100644 --- a/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc +++ b/fesco/modules/ROOT/pages/Package_maintainer_responsibilities.adoc @@ -22,7 +22,7 @@ Everyone that is a primary maintainer of a package in Fedora is also strongly en == Manage security issues -* Package maintainer should handle security issues quickly, and if they need help they should contact the link:https://fedoraproject.org/wiki/Category:Security_Team#Contact[Security Response Team]. +Package maintainer should handle security issues quickly, and if they need help they should contact the link:https://fedoraproject.org/wiki/Category:Security_Team#Contact[Security Response Team]. == Work with upstream @@ -61,9 +61,9 @@ It is recommended that non-coder packagers should find co-maintainers who are fa The link:https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Package update policy] provides guidance for maintainers updating packages on an already-released branch. In summary, however, maintainers should bear in mind that: -1. Many Fedora users update automatically, so it is most important that an update doesn't cause a users' applications or system to stop working suddenly. -2. Fedora users who do not update automatically may review the descriptions attached to updates before choosing whether they should apply them. -3. Not all Fedora users have good Internet bandwidth available and may prefer a single update with multiple changes rather than many updates in a short period. +* Many Fedora users update automatically, so it is most important that an update doesn't cause a users' applications or system to stop working suddenly. +* Fedora users who do not update automatically may review the descriptions attached to updates before choosing whether they should apply them. +* Not all Fedora users have good Internet bandwidth available and may prefer a single update with multiple changes rather than many updates in a short period. == Mentor and watch over co-maintainers @@ -78,23 +78,25 @@ See the link:https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packag == Track dependency issues in a timely manner -* In Rawhide, updates to packages may cause other packages to have broken dependencies. +In Rawhide, updates to packages may cause other packages to have broken dependencies. Maintainers will be alerted when this happens, and should work to rebuild their packages with all due haste. Broken dependencies may leave end user systems in a state where no updates will be applied. In order to keep the distribution in a reasonable state, someone will step in and rebuild packages that have had dependency issues for some time, but package maintainers should not rely on these rebuilds. == Notify others of changes that may affect their packages -* Some packages are depended upon by others; in this case, changes to one package may cause issues for others. +Some packages are depended upon by others; in this case, changes to one package may cause issues for others. Maintainers should be aware of the effects that changes to their packages may have, and should alert to the fedora-devel-announce mailing list of updates which contain ABI or API changes which may cause dependency problems for other packages. + The announcement should occur a week before the packages update, so all maintainers affected are notified. The announcement should include the following information: -** Nature of the change. -** Branches (Rawhide, F9, etc.) which will be affected by the change. -** Expected date of the change. -** List of packages which are affected by the change. + +* Nature of the change. +* Branches (Rawhide, F9, etc.) which will be affected by the change. +* Expected date of the change. +* List of packages which are affected by the change. Generally, this is merely the list of packages which depend directly on the package which is being updated, and can be found with `repoquery --whatrequires ` where `` is the package being updated. -** If your package upgrade breaks other packages in Rawhide, you should try to help fix the packages affected. +* If your package upgrade breaks other packages in Rawhide, you should try to help fix the packages affected. For example, if you're a provenpackager, queue the rebuilds yourself. == Respect Schedules