Hi Chris, we can pull stable once projects are done with the work on the release (i.e. release criteria is met) – i.e. it does not have to be the release date itself, but whenever a project feels like “ready”. One week prior to the release sounds reasonable – assuming you know when you’ll release ;-).
BTW/ - Releng already adopts this “don’t branch” principle – they didn’t even branch for Colorado. Frank From: Christopher Price [mailto:[email protected]] Sent: Dienstag, 13. September 2016 13:19 To: Frank Brockners (fbrockne) <[email protected]>; David McBride <[email protected]>; [email protected]; TECH-DISCUSS OPNFV <[email protected]> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule Hi Frank, I’m not sure the release date is realistic. Given the way we use stable branch in our CI and release processes it has been apparent that it takes around a week or more for the labels and artefacts to be generated from stable. I do think using a “window” for projects to progress to D release or not is valuable. I would suggest having the CI team provide guidance on the latest possible date to branch to stable for any release. (This depends on project adherence to CI processes and the processes themselves.) / Chris From: <[email protected]<mailto:[email protected]>> on behalf of "Frank Brockners (fbrockne)" <[email protected]<mailto:[email protected]>> Date: Tuesday 13 September 2016 at 12:42 To: David McBride <[email protected]<mailto:[email protected]>>, opnfv-project-leads <[email protected]<mailto:[email protected]>>, TECH-DISCUSS OPNFV <[email protected]<mailto:[email protected]>> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release] D-release schedule David, one thing that we’ve not closed on in the discussion last Tuesday is the stable-branching milestone. Per what Morgan and I elaborated on: Branching occurs a lot of unnecessary overhead for projects which have a single development stream only. Hence I’d like to propose that · the branching milestones *prior* to the release should *only* be applied to projects which do parallel development. · All other projects would branch on the release date – so that we have a proper maintenance branch. Thoughts? Thanks, Frank From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of David McBride Sent: Montag, 12. September 2016 23:52 To: [email protected]<mailto:[email protected]>; TECH-DISCUSS OPNFV <[email protected]<mailto:[email protected]>> Subject: Re: [opnfv-project-leads] [release] D-release schedule Reminder... if you haven't yet reviewed the schedule, please do so before the TSC and release meetings on Tuesday, where it will likely be discussed. David On Thu, Sep 8, 2016 at 3:45 PM, David McBride <[email protected]<mailto:[email protected]>> wrote: Team, I've posted an update to the schedule<https://wiki.opnfv.org/download/attachments/6827418/OPNFV%20Release%20%2522D%2522%20r2.pdf?version=1&modificationDate=1473367413338&api=v2>. Please review and provide feedback. Note: during the release meeting on Tuesday, we discussed removing the JIRA milestone, since it was not considered release gating. Since then, I've changed my mind. For the D-release, I expect that we will have implemented our JIRA processes sufficiently that we will be able to rely on JIRA to understand project status. Therefore, it is appropriate to believe that if we still have unresolved JIRA issues assigned to the release, then the release is not complete. We will be discussing exactly how this will be accomplished in the coming weeks. 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 -- 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]<mailto:[email protected]> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
