Changes between Version 1 and Version 2 of Developers/WorkingOnTickets

Timestamp:

2017-09-19T17:21:56+02:00 (7 years ago)

Author:

clevy

Comment:

--

Developers/WorkingOnTickets

@@ -21 +21 @@
 
 Each expert is requested to check regularly the list of open tickets in order to:
-* accept some assignments which are relevant to his expertise or good will
-* propose assignments for newly created tickets
+* [[span(''accept some assignments which are relevant to his expertise or good will'', style=color:lime)]]
 
-In fact, if we intend to have an up-to-date ticketing system, there should be nearly no tickets under "new" status, and each expert should have a few (more than one...) tickets assigned to him.
+* [[span(''propose assignments for newly created tickets'', style=color:lime)]]
 
+'''In fact, to have an up-to-date ticketing system, there should be nearly no tickets under "new" status, and each expert should have a few (more than one...) tickets assigned to him/her.'''
 
+Accepting assignments is indeed important in order to share a clear view on the list of tickets remaining to be taken in account.
 
+== Workflow for a given ticket
+Once an expert has accepted the assignment, the following items should be completed:
+* in the ticket, describe the chosen answer(s)
+* if some changes or fixes are to be commited in the NEMO reference, those should be tested before commit, including full SETTE tests in debug mode
+* in the comments of commit, do not forget the associated ticket number
+* check where commits are relevant (maybe at least 2 places: in the shared users version (3_6_STABLE for now) and in the trunk (version under development)
+* when tasks are completed, close the ticket