Skip to content

roadmap process

michaelkain edited this page May 4, 2022 · 8 revisions

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
  • State : specification

2) Consortium member vote

2.1) Estimation phase (4 weeks, in May, deadline 31.05.2022)

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

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

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

4) Documentation and production

When released, added to release notes

Clone this wiki locally