Greetings, During the TSC call, yesterday, I took an action to start an email discussion about the schedule for the E-release <https://wiki.opnfv.org/display/SWREL/E-River>.
Specifically, I suggested that we just plan for a single release, rather than three releases, as we've done in the past. Then, when the release date approaches, we evaluate whether we need a point release, then schedule it at that time. Why? - Scheduling three releases has created a lot of confusion with the project teams The purpose of the three releases is to give project teams time to debug and fix scenarios that are not ready for 1.0. They are *not* separate development timelines with separate release milestones. However, many believe that it isn't necessary to meet release milestones, because they will simply shift to the 2.0 or 3.0 release. - In the past two releases, the new content released in 2.0 has been minimal. For example, for Colorado 2.0, just two new scenarios were released. Human nature is such that, given the opportunity for a later deadline, many will take it. - Releases are not free. In addition to the overhead required for labeling, creating ISOs, and updating documentation, projects that released in previous releases, are required to update their code for subsequent releases to resolve any issues, even if they weren't intending to do any additional work on that major release. For example, let's say that a project releases in Danube 1.0, they're satisfied with their effort, so they shift their focus to the E-release. However, changes after 1.0 break their scenario. So, suddenly, they find themselves working on Danube 2.0, even though they aren't releasing any new scenarios. This process repeats for Danube 3.0. During the TSC call, it was suggested that a 2.0 or 3.0 release provides an opportunity to integrate a late release of a major upstream component (e.g. ODL). However, this is counter to our previous agreement not to change major upstream components after the 1.0 release. Unfortunately, this happened in Colorado and created significant disruption, including a slip in the 2.0 release. Per our discussion on Tuesday, I've created a wiki page <https://wiki.opnfv.org/display/SWREL/E-Release+Schedule+discussion> to capture pros and cons of various schedule options. Feel free to edit it and add your thoughts. David -- *David McBride* Release Manager, OPNFV Mobile: +1.805.276.8018 Email/Google Talk: [email protected] Skype: davidjmcbride1 IRC: dmcbride
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
