Proposed Simultaneous Release Plan
Ed Warnicke (eaw) <eaw@...>
I was asked by the TSC to send out the Proposed Simultaneous Release Plan we discussed
in todays TSC call to the list.
You can find it here:
I have made the following edits in response to requests from the TSC since we discussed it:
1) I have switched the mailing list in the Communication Channels section from 'simultaneous-release' to
2) I have added a 'String Freeze' to allow for internationalization to M5.
Rajeev Nagar raised a very important point that I am still not certain how to correctly incorporate,
but I feel should be: Where does documentation live in all of this? I am would love to hear thoughts as to how
to correctly incorporate that :)
Alejandro Avella <robertico.gonzalez77@...>
toggle quoted messageShow quoted text
I was wondering if you could provide some details on the test scenarios that you plan to run. Are they Junit test cases? What about for the Integration tests? Is there documentation for the unit and integration tests? Is there a test plan? Are there QA people involved in this Open Source project? How long does it take to run all the tests? Where can I find more information about how to test OpenDayLight project? I saw on the web page that the team is using Gerrit to trigger Jenkins jobs after code has been reviewed? What build tools are used in the project (Ant, Maven or others?)
I was trying to find this information on the wiki page, but I couldn't find it. If there is something already written, could you point me to that information?
On Thu, May 30, 2013 at 12:49 PM, Ed Warnicke (eaw) <eaw@...> wrote: