Version 5 (modified by nicolasmartin, 3 years ago) (diff)

Working on tickets

Last edition: 03/07/19 20:21:59 by nicolasmartin

Overview

The ticketing system for NEMO is quite active with about 160 ticket opened per year (reporting of last 12 months).

It is quite important to keep the ticketing system up to date, and thus to work on closing the tickets (with or without an associated commit) in an acceptable delay. This implies that all NEMO ST members and hopefully other developers (see list of involved developers/contributors) contribute to this work on a regular basis. This page describes the associated workflow and the responsibilities of each expert in these tasks.

Role and tasks of experts

Ticket workflow
de0849d0f263c422c872b63451b85ffd.png

Following the list of tickets

The list of open tickets needing some additional work is available here (where "Development branch" and "task" types have been excluded).

Each relevant ticket should be assigned to an expert, meaning that only actually new tickets should appear with "new" status, whereas all others should appear as "assigned".

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

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 some assignments

Accepting assignments is indeed important in order to share a clear view on the list of tickets remaining to be taken in account.

Resolving the issues

List of your opened tickets

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 committed 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

Current list of developers/contributors

sid

acc

agn

alexwestmohc

alistairsellar

anaguiar

andmirek

aumont

ayoung

cbricaud

cetlod

cguiavarch

charris

clem

clevy

clne

cmao

csanchez

dancopsey

davestorkey

dbruciaferri

dcarneir

deazer

dford

dguibert

diovino

djlea

emalod

emanuelaclementi

emmafiedler

epico

erwanraffin

flemarie

francesca

frrh

girrmann

gm

gsamson

hadcv

hadjt

hadlh

jamesharle

jcastill

jchanut

jenniewaters

jonnywilliams

jpalmier

jpaul

jsterlin

jwhile

kingr

kuniko

laurent

ldouriez

lovato

malcolmroberts

marc

mathiot

mattmartin

mcastril

mdrudi

mikebell

mocavero

nemo

niall

nicolasmartin

ohernandez

orioltp

pbarriat

pdavis

petesykes

phuot

rblod

rbourdal

rlod

rrenshaw

sciliberti

smasson

smueller

stefryn

stephenhaddad

techene

timgraham

tsearle

vancop

wayne_gaudin