20. GOP i - roadmap of future development

Proposal summary

Many projects have a roadmap of planned (or desired) future work. Should we use one? If so, what should go on it, bearing in mind our volunteer status? Is there any way of having a roadmap that isn’t vaporware?

The only thing I can see is to keep it extremely vague.

Rationale

We get questions about this. Let’s decide on an official answer.

Proposal details

Let’s adopt this as our development roadmap.

• 2.16: whenever we have 0 Critical issues. Expected late Sep or Oct 2011.
• 2.18: whenever we have 0 Critical issues, but not sooner than 2 months after 2.16. Expected Dec 2011 or Jan 2012.
• 2.18: whenever we have 0 Critical issues, but not sooner than 2 months after 2.18. Expected March-April 2012.
• GOP: currently running, expected to last until the end of 2011.
• GLISS: will not start until GOP is over. Almost certainly early 2012.

Implementation notes

None.

This document was generated by Graham Percival on June 13, 2012 using texi2html 1.82.