Blank Stable Release Tool Example

From OWASP
Revision as of 22:11, 20 June 2009 by Mtesauro (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Click here to return to the tool assessment criteria


Stable Release Review of [Project Name] [Release Name and Version]

Project Leader for this Release

[Project Lead]'s Pre-Assessment Checklist:

Alpha level

1. Is your tool licensed under an open source license?

2. Is the source code and any documentation available in an online project repository? (e.g. Google Code or Sourceforge site)

3. Is there working code?

4. Is there a roadmap for this project release which will take it from Alpha to Stable release?

Beta Level

5. Are the Alpha pre-assessment items complete?

6. Is there an installer or stand-alone executable?

7. Is there user documentation on the OWASP project wiki page?

8. Is there an "About box" or similar help item which lists the following:

  • Project Name?
  • Short Description?
  • Project Lead and contact information?(e.g. email address)
  • Project Contributors (if any)?
  • License?
  • Project Sponsors (if any)?
  • Release status and date assessed as Month-Year e.g. March 2009?
  • Link to OWASP Project Page?

9. Is there documentation on how to build the tool from source including obtaining the source from the code repository?

10. Is the tool documentation stored in the same repository as the source code?

Stable Level

11. Are the Alpha and Beta pre-assessment items complete?

12. Does the tool include documentation built into the tool?

13. Does the tool include build scripts to automate builds?

14. Is there a publicly accessible bug tracking system?

15. Have any existing limitations of the tool been documented?



First Reviewer

Second Reviewer

GPC/OWASP Board