Changes between Version 2 and Version 3 of UseOfTickets

Timestamp:

Jan 28, 2014, 3:12:29 PM (10 years ago)

Author:

Piero Campalani

Comment:

some formatting

UseOfTickets

@@ -1 @@
-This aims to be the central source of information about Tickets in rasdaman and their management.
+This aims to be the central source of information about ''Tickets'' in rasdaman and their management.
 
 = Tickets processing workflow =
 Along the lines of the built in [wiki:TracWorkflow trac workflow], with respect to ticket assignments we have in place:
- 1. If the ticket owner is not specified at the time of ticket creation, it gets assigned automatically to the component owner;
- 2. A ticket can then be assigned further to the person that would be the most appropriate for handling or solving it.
- 3. Once a person starts working on a ticket he has to "Accept" the ticket (so we are all aware that it is being worked on actively)
- 4. If on an accepted ticket one expects to stop working for long (e.g. more than 2-3 weeks) the ticket should be re-assigned (eventually to oneself)
-  * the ticket should be brought to a "stable" progress update point with an interim patch (to be confirmed)
+ 1. If the ticket '''''owner''''' is not specified at the time of ticket creation, it gets '''''assigned''''' automatically to the component owner;
+ 2. A ticket can then be '''''assigned''''' further to the person that would be the most appropriate for handling or solving it.
+ 3. Once a person starts working on a ticket he has to '''''accept''''' the ticket (so we are all aware that it is being worked on actively)
+ 4. If on an accepted ticket one expects to stop working for long (e.g. more than 2-3 weeks) the ticket should be ''re-assigned'' (eventually to oneself)
+  * the ticket should be brought to a "stable" ''progress update'' point with an interim patch (to be confirmed)
 
 From the above we have that:
- * Any ticket that is in "new or assigned" status can be sent to other people or anyone can volunteer to work on it (contacting the current owner for guidance or discussing it on the dev list is a good option for that);
- * Any ticket that is currently "Accepted" is expected to be under work and get either regular status updates or patch submissions towards its resolution. The owner of such a ticket has to be contacted before changes highly relevant to it are made or before reassignment or acceptance by someone else.
+ * Any ticket that is in '''new''' or '''assigned''' status can be sent to other people or anyone can volunteer to work on it (contacting the current owner for guidance or discussing it on the [MailingLists dev list] is a good option for that);
+ * Any ticket that is currently "Accepted" is expected to be under work and get either ''regular status updates'' or patch submissions towards its resolution. The owner of such a ticket has to be contacted before changes highly relevant to it are made or before reassignment or acceptance by someone else.
 
-Once a ticket is resolved and the patch submitted it can be closed with a reference to the changeset (so whoever wants to test it can see if it has already been integrated into the dev line or packaged for release.
+Once a ticket is '''resolved''' and the patch submitted it can be closed with a reference to the [WikiFormatting#TracLinks changeset] (so whoever wants to test it can see if it has already been integrated into the dev line or packaged for release).
 * Every patch referring to a ticket shall have a reference to it in the title/description for back reference.