-
-
Notifications
You must be signed in to change notification settings - Fork 12
Home
Carefully check for existing Issues; comment rather than opening a new Issue if possible. It may be advisable to sent email to the Arctos Group or Advisory Committee in conjunction with filing an Issue, but email (which becomes lost, diluted, or ignored) is never a suitable replacement for Issues.
Carefully check similar issues for similarities. It may be more appropriate to comment on an existing issue. Reference related issues with hashtag-issuenumber (#99999).
When filing an issue that you don't intend to fix immediately, leave Assignee blank. It's fair game for everyone else to ignore "assigned" issues.
Assign one of the following Milestones to every Issue. Adding Milestones to Issues lacking them should be a priority for everyone.
- Needs Discussion: The path to implementation is unclear.
- Active Discussion: The AC has begun discussions, or emails have been sent to the Arctos group.
- Next Task: The development needed is well-defined and accepted; just needs code written.
- Active Development: Code is being written. Use this as development begins; make sure an Assignee is listed.
- Wish List: Major development, or development requiring major funding.
- Wont Fix: The Issue has closed without action; use only for Closed Issues. Leave verbose comments when using this.
Please mark all resolved Issues as Closed.
Note that the functionality built into Labels at Google Code has mostly been replaced by Milestones. Please update this document before using any Labels not described below.
- Priority-Critical: Issue is causing major problems; corrupting data, crashing servers, etc.
- Priority-High: Issue is actively preventing progress.
- Priority-Normal: Standard Issue
- Priority-Low: Needs fixed/implemented/discussed, eventually.
Look right for subpage tree!
If you are looking for Documentation and other information on Arctos Collaborative Collection Management Solution, visit our extensive Arctosdb.org site.