Is there a program for the plugfest, like what happens which day? I only see few topics on email or etherpads (for the test wg) with no information about the date. Can someone provide an overview of the typical plugfest agenda? If I can attend, I may not be able to stay the whole week (likely at most 3 days) so for me I need to know rather quickly which 3 consecutive days are of interest to me.
Thanks Alec From: <[email protected]> on behalf of David McBride <[email protected]> Date: Wednesday, October 4, 2017 at 1:45 PM To: TECH-DISCUSS OPNFV <[email protected]> Cc: Raymond Paik <[email protected]>, Trevor Bramwell <[email protected]>, Aric Gardner <[email protected]>, opnfv-project-leads <[email protected]>, Tapio Tallgren <[email protected]> Subject: [opnfv-project-leads] [release] improving branch process Team, This will be a topic at our upcoming plugfest (Dec 4 - 8), but I'd like to start the discussion now with the goal of having a draft proposal that we can review and finalize at plugfest. We can discuss this on the mailing list and I will also devote some time to it during the weekly release call. In both the Danube and Euphrates releases, the process of enabling CI and test on the branch has taken as long as two weeks to complete, following MS7. As a result, we are left with just a few days to fix remaining bugs and finalize the scenarios prior to the release date. Therefore, as a starting point, I'd like to propose the following: 1. Reduce the branch window from 2 weeks to 1 week, thereby pulling in MS7 by one week. 2. Trevor B has told me that many of the activities that, in the past, we've waited until MS7 to complete, could actually be done before MS7. So, let's address the following: o What activities must be performed when we branch (detailed description), such that we have builds, testing, and the test results dashboard operational on the branch? o Do each of those activities have an owner? o Which of these activities could be performed prior to MS7? I'd like to set a goal of having builds, test, and test results dashboard operational on the branch within 3 business days following the branch. That is, if the branch occurs on a Friday, then we are operational on the branch by COB on the following Wednesday. Here's what (I think) I know about what must be done when we branch. Please correct and fill in the details, including who owns the task. Also, please comment on whether a task can be done in advance of branching. 1. Update docker yaml file 2. Enable testing (RELENG repo) 3. Create Jenkins jobs for branch for each installer 4. Update the test results dashboard I think that we can shave at least a week off of this process. That, in combination with pulling MS7 in by a week should give our team sufficient time to complete the release. I appreciate your input. David -- David McBride Release Manager, OPNFV Mobile: +1.805.276.8018<tel:%2B1.805.276.8018> Email/Google Talk: [email protected]<mailto:[email protected]> Skype: davidjmcbride1 IRC: dmcbride
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
