roadmap process

Roadmap process

Current roadmap issues: Roadmap

1) Create an issue in GitHub

• Issue == (bug or feature), that could become part of the roadmap and label it "ROADMAP"
• Important bugs are not voted, but directly fixed
• Alternative : send email to Julien and Michael
• as agreed by the consortium, as our GitHub is public, the discussions on roadmap issues are open and anybody (members and not-members) can propose issues for the roadmap and take part in the discussions on the issues, to state its opinion
• State: specification

2) Vote of consortium members

2.1) Vote preparation phase (4 weeks, in May, deadline 31.05.2022)

• List of issues send to members, wait 4 weeks to complete with ideas
• Members and Inria declare issues interesting for them
• Collect ideas of all members and affine them
• Developers complete and estimate items identified as interesting for members
• State: estimated

2.2) Actual vote phase (2 weeks in June, 01.06.-15.06.2022)

• Developers estimate potential development volume for this vote, as updates and fixes might be necessary, that will require time too
• Only estimated and fully specified issues come to the vote
• Voting for roadmap of 6 months (01.07. - 31.12.2022)
• Summary of completed list, send for vote
• 2 weeks for votes
• State: voted

2.3) Roadmap established, put online (deadline 31.06.2022)

• Summary of vote shared by developers
• Issue is labelled with a release version and a date, when it comes

3) Issue changes to dev, then review and test

• Development starts
• States: development, review, test

4) Documentation and production

Documentation is done for each issue, when released, added to release notes

• States: documentation and production

Roadmap issue states

• specification -> GitHub issue created and tagged with "ROADMAP"

• estimated Issue has been identified as interesting by at least one member and will therefore be finished as specification and estimated in terms of dev effort.

• voted An issue has officially been voted on the roadmap and will be tagged with an upcoming release number and date, when it will be released.

• development dev only starts, when item has been voted by the consortium members

• review PR in review from another developer

• test (in develop, but not yet in master) often on qualif env, for test

• documentation extend GitHub Wiki to complete doc on new feature

• production part of master and added to release notes

Effort estimations

Dev efforts in t-shirt sizes:

• [S]: 1-3 work days
• [M]: 4-5 days (1 week)
• [L]: 6-10 days (2 weeks)
• [XL]: 11-20 days (4 weeks)
• [XXL]: 21-40 days (2 months)
• [XXXL]: 40+ days (> 2 months)