Differences

This shows you the differences between two versions of the page.

--- pear:qa:policy [2008/11/24 13:30] – created clockwerx
+++ pear:qa:policy [2017/09/22 13:28] (current) – external edit 127.0.0.1
@@ Line 63: / Line 63: @@
 Package maintainers can also grant QA the rights to make a releases for their packages.
-==== pearweb QA subsection ====
-It seems that there is a lack of QA material in the manual that people agree on and there is also need to make it move visible for people so they will actually follow those rules/guidelines. The QA team will therefore get its own QA subsection in the manual and will have control over it just like package maintainer controls package related docs in the manual. The QA team also gets its own subsection on pearweb so people can more easily access QA material which is too dynamic or just related to the QA team own internal documentation purposes. There the QA will, for example, publish their latest decisions. Furthermore here the QA team will be able to provide interfaces to QA team services. For example, here the QA team could offer an interface for maintainers to configure the access rights they want to grant the QA. Finally the core QA team can add QA related notes to each package homepage to communicate QA related information to the user base.
 ==== Approving first stable release ====