Package Maintainers: Difference between revisions

Latest revision as of 19:53, 30 June 2023

This material is work-in-progress ...

Do not follow instructions here until this notice is removed.
(Last edited by Psykose on 30 Jun 2023.)

You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what FreeBSD does)
The maintainer is responsible for the package and is expected to:
- fix bugs in their package
- keep it updated. This includes following upstream announcement list, RSS feeds etc., and providing updates to Alpine Linux in a timely fashion.
  - it seems easier for maintainers to add their packages Anitya for automated release monitoring
Committers and others should confirm with the maintainer before making any changes to the package.

@@ Line 2: / Line 2: @@
 * You can be maintainer without having commit access. Committers can do commits and maintainers can send patches to committers. Any committers can apply patches from maintainers. (This is similar to what FreeBSD does)
-* The maintainer is responsible for the the package and is expected to:
+* The maintainer is responsible for the package and is expected to:
-** fix bugs in package
+** fix bugs in their package
-** keep it updated. This includes follow upstream announcement list, RSS feed etc and provide updates to Alpine Linux in timely fashion.
+** keep it updated. This includes following upstream announcement list, RSS feeds etc., and providing updates to Alpine Linux in a timely fashion.
-* Committers and others should confirm with the maintainer before making any changes of the package.
+*** it seems easier for maintainers to add their packages [https://release-monitoring.org/ Anitya] for automated release monitoring
+* Committers and others should confirm with the maintainer before making any changes to the package.
 [[Category:Development]] [[Category:Package Manager]]