Tracker: Bugs
Skip guidelines
Tracker Guidelines
Rules to follow when administrating tracker items.
Groups
If you are testing 1.x from subversion, post the bug in phpws1.x.
Sorry for the extra groups. We can't delete them.
Sourceforge tracker summary and priority guidelines:
Summary Tagging: All phpwebsite tracker summaries are to be tagged with the following set of tags. They should be used in two levels, the second level being optional.
Top Level Tags:- UI
- User Interface
- DB
- Database
- I18N
- Internationalization
- PREF
- Preference or Setting
- WAI
- Web Accessibility Initiative
- XHTML
- Extensible HyperText Markup Language
- PEAR
- PHP Extension and Application Repository
- PHP
- HyperText Preprocessor
- SEM
- Semantic Web
- UNK
- Unknown (needs further comment)
- NEW
- New to the code base
- REV
- Requires a code base revision
- COM
- Compliance issue
Priority Definitions:
The priority values have special meaning when they are a phpwebsite tracker items. The meanings are described below:
- Duplicate, Invalid, Out of Date, Rejected, Wont Fix, Works For Me
- To be implemented on a rainy day
- ...
- ...
- To be implemented in the current group assignment, but can be moved to the next group. If item is moved priority must be bumped up.
- ...
- ...
- ...
- Must be implemented in the current group assignment
Priorities 3,4...6,7,8 are left to the developers for sorting their individual items.
About SourceForge
Develop Software
Community
Copyright © 2009 Geeknet, Inc. All rights reserved. Terms of Use
