Yujun,
Well, we don't have much new features in Danube. We need documentation and testing improvements in Danube. Those are not easy to be mapped in an overview picture. We wrote down the release plan while we didn't have JIRA and guidelines at the early stage of OPNFV. The original plan and figure could be kept, but I prefer to update that part with what we requires currently and move the overview of old releases into an appendix for archive. BR, Ryota > -----Original Message----- > From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] > Sent: Wednesday, November 23, 2016 3:59 PM > To: TECH-DISCUSS OPNFV <opnfv-tech-discuss@lists.opnfv.org> > Cc: Mibu Ryota(壬生 亮太) <r-m...@cq.jp.nec.com> > Subject: ##freemail## [doctor] Danube plan overview > > Hi doctors, > > I'm reviewing the requirement document for an internal presentation. There is > a release plan for Arno and it looks > good[1]. > > We have already sorted out the working items for Danube release, but it would > be better if we can have an overview > about the goals we want to achieve. > > @Ryota, what do you think? > > [1]: > http://artifacts.opnfv.org/doctor/docs/requirements/index.html#implementation-plan-for-opnfv-release-1 > [2]: https://wiki.opnfv.org/display/doctor/Danube+Planning _______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
