List view

• Release 2.68.0

  No due date

  •9/9 issues closed
  100% complete0 open9 closed

• Next Release

  No due date

  •6/11 issues closed
  54% complete5 open6 closed

• 3a Needs Implementation discussion

  After an issue has reached a consensus among all stakeholders, implementation details have to be discussed with the vendor. Once done, the issue is ready for implementation.

  No due date

  •26/54 issues closed
  48% complete28 open26 closed

• 4 Ready for Implementation

  Last milestone before milestone "Next release". The predecessor is "Consensus Finalized".

  No due date

  •51/91 issues closed
  56% complete40 open51 closed

• 3 Consensus Finalized

  When an issue is at milestone "Consensus reached" PC members have the opportunity to oppose for five days. If no one objects the issue is moved forward to Consensus Finalized. Issues here wait for implementation details fo be sorted out. The next milestone is "Needs Implementation Discussion"

  No due date

  •10/12 issues closed
  83% complete2 open10 closed

• 2 Consensus Reached

  Issues that are in the Consensus queue. When a decision is made about how an issue will be dealt with by the Product Committee, the issue is moved to "Consensus Reached" Next milestone is "Consensus Finalized" Previous milestone is "Decide"

  No due date

  •8/11 issues closed
  72% complete3 open8 closed

• 1 Decide

  Issues under Decide queue. Issues are kept in Decide while the Product Committee discusses the issue. Next milestone is "Consensus Reached"

  No due date

  •211/292 issues closed
  72% complete81 open211 closed