[Documentation] [TitleIndex] [WordIndex


Package proposal

Fill this section in with your proposal for the package, and send the link to this page out for discussion.

Keep this section up to date over the course of the email conversation until the proposal is accepted.

When appropriate, add a parallel "API proposal" section



Overall, pretty good. It answers my original complaints with the pr2.xml syntax with respect to templates not really being templates as they did not have variables. This is very similar to the Apache ant spec, at least with respect to defining and instantiating variables. The main things I would consider:

Package review meeting notes

Create new package review

Enter the date in the appropriate box to generate a template for an API or code review meeting. Check the QAProcess page for more information.

2019-07-13 13:21