|
|
|
# Gitlab usage
|
|
|
|
|
|
|
|
## General dev workflow
|
|
|
|
|
|
|
|
- Issue created with label ``status::TODO``
|
|
|
|
- Issue attributed to a dev
|
|
|
|
- Assigned dev works on issue to detail dev to do (specification, code sample test to add, todo list (=child issue))
|
|
|
|
- Move label issue from ``status::TODO`` to ``status::WIP``
|
|
|
|
- Create local branch + MR (in MR title add ``Draft:<MR title>`` or check the draft checkbox when creating/editing) + mention issue in MR
|
|
|
|
- When the MR is ready remove the tag Draft from the title
|
|
|
|
- When every MR is ready move label issue from ``status::WIP`` to ``status::Review Ready``
|
|
|
|
- Review process
|
|
|
|
- Merge MR
|
|
|
|
- When every MR is merged, close issue
|
|
|
|
- Make sure to close every child issue before closing the main issue
|
|
|
|
|
|
|
|
## Global workflow
|
|
|
|
|
|
|
|
- For each release, create a Milestone
|
|
|
|
- Add list of things to do
|
|
|
|
- Create related issues and assign dev
|
|
|
|
- Each week check issue board
|
|
|
|
- Week before dead line, create changelog
|
|
|
|
- Release :rocket:
|
|
|
|
|
|
|
|
## Handling of ticket issues
|
|
|
|
|
|
|
|
Ticket issues are issues related to a bug.
|
|
|
|
|
|
|
|
- The issue must be created with no ``status`` tag
|
|
|
|
- During a weekly these issues are ranked by priority by the dev team
|
|
|
|
- Some issues will be assigned depending on the passign band of the team, this is symbolized by adding the label ```status::TODO``.
|
|
|
|
- Check **General dev workflow** for the next steps !
|
|
|
|
|
|
|
|
## How to set labels
|
|
|
|
|
|
|
|
Label are not set for Merge Request, only for Issues !
|
|
|
|
|
|
|
|
* status: these labels help to sort
|
|
|
|
* TODO: issue need to be treated
|
|
|
|
* WIP: issue has been assigned and break down in to actions, a dev is working on it !
|
|
|
|
* Review ready: MR fixing the issue have been done and need to be reviewed
|
|
|
|
* Discussion: issue with this label are here to propose modification/new features
|
|
|
|
|
|
|
|
Incoming ...
|
|
|
|
|
|
|
|
## Using issue board
|
|
|
|
|
|
|
|
Aidge project manage developpement using the GitLab issue system.
|
|
|
|
|
|
|
|
You can find the issue board here: https://gitlab.eclipse.org/groups/eclipse/aidge/-/boards/3169
|
|
|
|
|
|
|
|
There are mulitple issue boards:
|
|
|
|
* Development: Show issues sorted by status
|
|
|
|
* Discussions: Show issues requiring a discussion |
