Package Maintainers: Difference between revisions
(initial notes on whats expected from package maintainers) |
(draft) |
||
| Line 1: | Line 1: | ||
{{Draft}} | |||
* 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) | * 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 the package and is expected to: | ||
Revision as of 02:51, 3 November 2010
 Do not follow instructions here until this notice is removed. |
- 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:
- fix bugs in package
- keep it update. This includes follow upstream announcemt list, rss feed etc and provide updates to Alpine Linux in timely fashion.
- Committers and others should confirm with the maintainer before making any changes of the package.