Issue management

[franck-ledoux]

I just added 3 template for issues:

• bug report
• feature request
• documentation request
  It is a first proposal. I would tend to add
• Quality code improvement request to gather issues whose topics are test, CI, source management (external project), build system and so on. What do you think?

I also start to work on defining labels we should use for all our issues. I think they could be:

• bug_fix (already provided in GitHub as "bug")
• quality_improvement or split into
  - CI
  - code_coverage
  - refactoring
  - Programming improvement
• new_feature (already provided in GitHub with the name "enhancement" that I don't like so much)
• documentation (already provided in GitHub)

We can in practice only keep the label we want for the project (https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels). It is interesting to suggest that every issue must be opened with a given label

[franck-ledoux]

Considering how we work, I would also like to use milestones to manage development in slots of 4 to 5 weeks (like a scrum sprint). Just in order to coordinate our development

[franck-ledoux]

3 types of labels

1. Bug, feature, Help, Doc, quality
2. Blocking, smooth, quadmesher, aero
3. Priority: Low, high

[franck-ledoux]

Add milestones with deadlines and tasks to perform.