PHP Wiki - pear:qa

bug_triage

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2012/04/12 23:32		current
Line 31:		Line 31:
	In general, we encourage the use of an appropriate phpunit.xml - we target PHPUnit 3.6 at this time.		In general, we encourage the use of an appropriate phpunit.xml - we target PHPUnit 3.6 at this time.

-	Your package directory layout should allow you to successfully run your test suite as below:	+	Your package directory layout should allow you to successfully run your test suite as below (assuming svn):
	<code bash>		<code bash>
	$ cd Foo_Bar/trunk		$ cd Foo_Bar/trunk

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/17 05:30		current
Line 23:		Line 23:


-	'''Items which I don't know where to place:'''	+	==== Items which I don't know where to place: ====
	- <del>Decide on a move to a set/book structure, and where the sets/books are separated at (categories/collectives, or individual packages)</del> - done, cweiske		- <del>Decide on a move to a set/book structure, and where the sets/books are separated at (categories/collectives, or individual packages)</del> - done, cweiske
	- <del>what, semantically is involved in this - docbook reference</del> - done, cweiske		- <del>what, semantically is involved in this - docbook reference</del> - done, cweiske
Line 38:		Line 37:
	This is a start at a conversion script, which will handle almost all of step 4 above.		This is a start at a conversion script, which will handle almost all of step 4 above.

-	'''Execution examples:'''	+	==== Execution examples ====

-	Convert all files $	+	Convert all files
	<code>./peardoc_conversion.sh</code>		<code>./peardoc_conversion.sh</code>

-	Convert one file $	+	Convert one file
	<code>./peardoc_conversion.sh peardoc/en/chapters/installation/shared.xml</code>		<code>./peardoc_conversion.sh peardoc/en/chapters/installation/shared.xml</code>

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2017/09/22 13:28		current
Line 1:		Line 1:
-	{{{INSIGHTFUL TEXT HERE}}}	+	====== Add some insightful text here ======

Anonymous (anonymous@undisclosed.example.com) — 2025-04-03T13:08:43+00:00

2008/11/24 13:30		current
Line 63:		Line 63:
	Package maintainers can also grant QA the rights to make a releases for their packages.		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 ====		==== Approving first stable release ====