← Prev in month ← Prev in thread
Next in thread → Next in month →

Updated issue tracker proposal

From
Al Brown <>
Date
2008-12-08T17:43:19+00:00
ID
Thread
Updated issue tracker proposal
http://wiki.oasis-open.org/cmis/IssueTracker has been updated per today's discussion:  The page is posted below:

Guidelines

Issues added at least 7 (calendar) days before a TC meeting will be reviewed before the next meeting, i.e. one of the following things will happen: 

If a resolution can already be reached (e.g. it’s just fixing a “bug”, etc.), it will be done in mail before the next meeting. 

If anyone disagrees with the resolution, we can discuss it at the next meeting. 

If the proposal is substantive (ie, not a typo) it should be discussed at the next meeting. If there is any question on the substantive nature of an issue, it should be treated as substantive. 

If further clarification/discussion is needed, it will either be done in mail before the next meeting. 

If no consensus is reached on the list before the next meeting, the issue will be added to the agenda for the next meeting. 

Responsibilities: 

Proposer: It is the proposers responsibility to make sure his or her proposal is discussed, received adequate reviews, and voted on at the TC meeting. 

Component Owner: It is the owners responsibility to look at across all issues for his or her componentand provide holistic feedback and validate issues do not conflict. 

Fields: 

Description: Describes the issue with any relevant context. This field should only be edited by the reporter to clarify the issue being reported 

Proposal: This describes the proposed resolution of the issue. This field will be kept up to date based on the comments and will be updated by either the reporter or by the owner of the component. 

Resolution: This describes the resolution of the issue when it is closed. This is edited by the owner of the component. If the resolution field contains a resolution, the Fixed Version must specify which version will contain this resolution. 

Creating issues: 

Issues should address a single item that can be resolved 

Issues that contain more than one item will be updated to reflect a single item 

Issues should be created to capture a discussion. A thread should be created on the mailing list and any issues that arise should be created in the issue tracker. 

Editing Issues: 

When editing issues, please add comments instead of editing. 

Links

Tracker - http://www.oasis-open.org/committees/cmis/

-Al

Al Brown

ECM CTO Staff, Information Managament

Office     714 327 3453

Mobile   714 263 6441

Email     

CONFIDENTIAL NOTICE: The contents of this message, including any attachments, are confidential and are intended solely for the use of the person or entity to whom the message was addressed. If you are not the intended recipient of this message, please be advised that any dissemination, distribution, or use of the contents of this message is strictly prohibited. If you received this message in error, please notify the sender. Please also permanently delete all copies of the original message and any attached documentation.
← Prev in month ← Prev in thread
Next in thread → Next in month →