+1, and with it we probably need to have an idea on how to populate the roadmap page.
I could imagine a page with three sections, something along the lines of Kafka <https://cwiki.apache.org/confluence/display/KAFKA/Future+release+plan> or Hive <https://cwiki.apache.org/confluence/display/Hive/Roadmap>. 1. Features/bug fixes of the next release. This list would be maintained by the current Release Manager. 2. Features/bug fixes beyond the current release that are in progress and that have an assigned owner (or owners). 3. Features/bug fixes that are unassigned but that we would like to get done. Sections 2 and 3 could be a community effort. I would suggest putting this into the wiki, to allow the community to edit it - I hope we won't need a more formal process. In a way, of course, the roadmap already exists, in JIRA: Here is a list of open requests for new Trafodion features <https://issues.apache.org/jira/issues/?jql=project%20%3D%20Trafodion%20AND%20resolution%20%3D%20Unresolved%20AND%20Type%20%3D%20%22New%20Feature%22%20ORDER%20BY%20updatedDate%20DESC> and a list of open improvements <https://issues.apache.org/jira/issues/?jql=project%20%3D%20Trafodion%20AND%20resolution%20%3D%20Unresolved%20AND%20type%20%3D%20Improvement>. The roadmap page would have a subset of those and maybe also some important bug fixes? Thanks, Hans On Thu, Jul 14, 2016 at 8:00 AM, yang theseus <[email protected]> wrote: > +1 > > 2016-07-14 22:21 GMT+08:00 Yang, Yang (Felix) <[email protected]>: > > > +1 > > > > > > > > 在 "Liu, Ming (Ming)" <[email protected]>，2016年7月14日 下午8:35写道： > > > > Hi, all, > > > > I suggest that Trafodion team should add a 'roadmap' page in the > project's > > front web page, so users will be clear what to expect in the future. > > It will help decision making in some cases. > > > > Thanks, > > Ming > > > > >
