Package Maintainers: Difference between revisions
mNo edit summary |
m (spelling fixes) |
||
| Line 1: | Line 1: | ||
{{Draft}} | {{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 | * 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: | ||
** fix bugs in package | ** fix bugs in package | ||
** keep it updated. This includes follow upstream | ** keep it updated. This includes follow upstream announcement 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. | * Committers and others should confirm with the maintainer before making any changes of the package. | ||
[[Category:Development]] [[Category:Package Manager]] | [[Category:Development]] [[Category:Package Manager]] | ||
Revision as of 08:25, 18 March 2018
 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 updated. This includes follow upstream announcement 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.