Changes between Version 6 and Version 7 of Developers/Working On Tickets


Ignore:
Timestamp:
2017-09-21T14:15:55+02:00 (3 years ago)
Author:
clevy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Developers/Working On Tickets

    v6 v7  
    2626 
    2727Each expert is requested to check regularly the list of open tickets in order to: 
    28 * [[span(''accept some assignments which are relevant to his expertise or good will'', style=color:green)]] 
    29 * [[span(''propose assignments for newly created tickets'', style=color:green)]] 
     28* [[span(''accept some assignments which are relevant to his expertise or good will'', style=color:red)]] 
     29* [[span(''propose assignments for newly created tickets'', style=color:blue)]], see list of experts below 
    3030 
    3131'''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.''' 
     
    3737=== Resolving the issues 
    3838 
    39 [/query List of your opened tickets] 
     39Each expert should aim at closing tickets: 
     40[/query List of the tickets assigned to you] 
    4041 
    4142Once an expert has accepted the assignment, the following items should be completed: 
    42 * in the ticket, describe the chosen answer(s) 
    43 * if some changes or fixes are to be committed in the NEMO reference, those should be tested before commit, including full SETTE tests in debug mode 
    44 * in the comments of commit, do not forget the associated ticket number 
    45 * 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) 
    46 * when tasks are completed, close the ticket 
     43* In the ticket, describe the chosen answer(s) 
     44* If some changes or fixes are to be committed in the NEMO reference, those should be tested before commit, including full SETTE tests in debug mode 
     45* In the comments of commit, do not forget the associated ticket number 
     46* 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) 
     47* When tasks are completed, close the ticket 
    4748}}} 
    4849