> > I think of a roadmap as a pre-CEP activity for upcoming releases, items > thereon beginning the CEP process, … >
What about having it the other way around? That the roadmap is a visualisation of the CEPs, i.e. those past initial triage that have initial commitment and momentum. A reflective approach of the roadmap, just a visualisation of existing processes, prevents the adding of a new process to the community. It will also incentivise the thoroughness of new CEPs. The benefit of having the roadmap as a separate manual process pre-CEP might save us the cost of creating CEPs that get rejected, but I can't see that actually being a problem for us. +1 to having the roadmap, in any form.
