This evening I facilitated a call between the Integration team, the LF Release Engineering team, and several folks from the development community. This was an action item from Monday’s PTL meeting. The “quick 1/2 hour call" ran for just short of 2 full hours, so there was plenty of discussion around these recommendations. This will be reviewed as part of the version and branching decisions at the TSC meeting on Thursday.
In order to ensure we make the release date the following steps are being recommended by the people on the call: — Follow the recommendations presented last week which will be voted on Thursday. https://wiki.onap.org/download/attachments/15993187/ONAP-versioning_discussion_26Oct2017.pdf?version=1&modificationDate=1509033560000&api=v2 <https://wiki.onap.org/download/attachments/15993187/ONAP-versioning_discussion_26Oct2017.pdf?version=1&modificationDate=1509033560000&api=v2> From now on only high/highest priority bugs against MVP projects should be COMMITTED into the repos. Other code can be SUBMITTED to gerrit, but not committed and should not be considered for Amsterdam The definition of high/highest priority bugs can be found here: https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-JIRADefectDefinition <https://wiki.onap.org/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-JIRADefectDefinition> Daily Integration meeting calls are being held to determine testing priorities for the day. PTLs with outstanding high/highest priority bugs must attend to help jointly decide what may be Committed. Meeting time is 7:30 AM Pacific. https://zoom.us/j/4466668888 <https://zoom.us/j/4466668888> As of Thursday Nov. 9 the Integration team will ONLY be testing against code in the Nexus Release repo. PTLs must formally release both the maven artifacts and Docker artifacts to be tested. This implies several things in terms of the actual release process: Some manner of self assessed stressed testing has been performed against the code in STAGING by the development team The PTL has made the decision that the code is stable and ready to be released The PTL opens a ticket with [email protected] to promote maven artifacts from the STAGING repo into the RELEASE repo. This ticket must include specific Jenkins job that produced the artifacts they want released LF Release Engineering will take that information and: sign the maven artifacts that were produced push a signed tag into the repository on the commit that produced the artifacts release the staging repository into the releases repository. The development team should have their docker build utilize newly released artifacts and pull those artifacts into their docker image. A new build should be then be triggered. The development team should do any stability testing of their docker image they feel is needed Upon PTL’s decision that the docker image is also good, the PTL opens a ticket with [email protected] to promote the docker artifact, similar to what was done for the maven artifact. LFRE will: Migrate the docker image from the snapshot / staging docker repository into the docker release repository. Push the images into docker hub when appropriate Normally here I would say something like, “Please let me know if you have any questions”, but I'm probably not the right person to be fielding most of the questions that are likely to be generated by this thread. ;-) If you are looking for clarification on something related to this, please just reply and the appropriate party will respond. Best Regards, -kenny Kenny Paul, Technical Program Manager [email protected] 510.766.5945
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
