This was completed Thanks! Jess
On Wed Jun 06 02:04:59 2018, [email protected] wrote: > Dear Jessica, > > Sorry for late, > > https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers- > javatoscachecker-master-javatoscachecker-release-version-java- > daily/209/ > https://jenkins.onap.org/view/modeling/job/modeling-toscaparsers- > nfvparser-master-nfvparser-release-version-java-daily/127/ > > thanks > > DENG Hui > > > -----Original Message----- > From: Jessica Wagantall via RT [mailto:onap- > [email protected]] > Sent: Wednesday, June 6, 2018 1:00 PM > To: denghui (L) <[email protected]> > Cc: Gildas Lanilis <[email protected]>; [email protected]; > [email protected]; [email protected]; > [email protected]; [email protected]; > [email protected] > Subject: [ONAP Helpdesk #56955] RE: [onap-discuss] Beijing Release: > Last Mile > > Dear Deng, > > Thanks, but I need you to give me the links to the Jenkins jobs that > generated these please. > > I cannot perform a release without them. > > Thanks! > Jess > > On Tue Jun 05 22:48:45 2018, [email protected] wrote: > > Hi Jess, > > > > This is for modeling part, thanks a lot: > > > > Javatoscachecker: /org/onap/modeling/toscaparsers/Checker/1.2.0- > > SNAPSHOT/Checker-1.2.0-20180605.124309- > > 60.jar<https://nexus.onap.org/service/local/repositories/snapshots/con > > tent/org/onap/modeling/toscaparsers/Checker/1.2.0- > > SNAPSHOT/Checker-1.2.0-20180605.124309-60.jar> > > NFVParser: /org/onap/modeling/toscaparsers/nfvparser/modeling- > > toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers- > > nfvparser- > > 1.1.0-20180329.050338- > > 7.zip<https://nexus.onap.org/service/local/repositories/snapshots/cont > > ent/org/onap/modeling/toscaparsers/nfvparser/modeling- > > toscaparsers-nfvparser/1.1.0-SNAPSHOT/modeling-toscaparsers- > > nfvparser- > > 1.1.0-20180329.050338-7.zip> > > > > Deng Hui > > > > From: [email protected] [mailto:onap-discuss- > > [email protected]] On Behalf Of Jessica Wagantall > > Sent: Wednesday, June 6, 2018 6:16 AM > > To: Gildas Lanilis <[email protected]> > > Cc: [email protected]; [email protected] > > Subject: Re: [onap-discuss] Beijing Release: Last Mile > > > > No request received yet also from the modeling team. > > > > Thanks! > > Jess > > > > On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall > > <[email protected]<mailto:[email protected]> > > > > > wrote: > > Dear Gildas, > > > > Here is an update on the pending items: > > > > *** MUSIC *** New release version 2.5.5 needed *** > > > > - Working with Tom on this now. We should be releasing soon. > > Reference: #56927: Music Jar Release 2.5.5 > > > > *** VID *** New clarification from the team *** > > > > - The request was placed to make a docker release but I noticed > > their maven artifacts haven't been released for the specific > > version > > used > > to build their docker images. Do we approve a release of those too? > > Reference: #56922: VID docker release > > > > *** AAF *** Pending Ram's Approval *** > > > > - Docker release for onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0 > > - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014- > > 8.jar<https://nexus.onap.org/index.html#view- > > repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms- > > client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar> > > Reference: #56662: Artifacts for Release > > > > No release request yet from multicloud or usecase-ui teams! > > > > Thanks! > > Jess > > > > On Mon, Jun 4, 2018 at 12:27 PM, Jessica Wagantall > > <[email protected]<mailto:[email protected]> > > > > > wrote: > > Thanks a lot for this Gildas, > > > > Due to the importance of these releases, I will help posting here the > > blockers we encounter in the RT tickets. > > > > Here are some blockers: > > > > *** AAF *** Pending Ram's Approval *** > > > > - Docker release for onap/aaf/sms and onap/aaf/smsquorumclient 2.0.0 > > - Java artifacts 2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014- > > 8.jar<https://nexus.onap.org/index.html#view- > > repositories;snapshots~browsestorage~/org/onap/aaf/sms/sms- > > client/2.0.0-SNAPSHOT/sms-client-2.0.0-20180530.111014-8.jar> > > Reference: #56662: Artifacts for Release > > > > *** DMAAP *** Pending Ram's Approval *** > > > > - Docker release for onap/dmaap/dmaap-mr:1.1.4 > > Reference: #56857: Move docker image to release repository > > > > *** VFC *** Yan to clarify *** > > > > - Email sent for 8 maven artifacts to be released, but email mentions > > also docker images needed and no link to docker images jobs > > - Do we just need to release the maven artifacts? if docker images > > need release, please update request with corresponding docker links > > from Jenkins > > Reference: #56821: Please help to release VF-C R2 artifacts to > > releases repo > > > > > > Thanks! > > Jess > > > > On Mon, Jun 4, 2018 at 7:33 AM, Gildas Lanilis > > <[email protected]<mailto:[email protected]>> wrote: > > Hi PTLs, > > > > This email is to summarize on the latest activities to reach Beijing > > Release Sign-Off this Thursday, June 7, 2018. > > > > 1. Docker image: All projects that need to Release a new Docker > > Image (and thus update accordingly the Docker manifest file) must > > email LF Helpdesk by 2 pm PDT on Tuesday, June 5 including a link to > > the proper specific Jenkins build job that generated the selected > > candidate build (e.g. > > https://jenkins.onap.org/view/oparent/job/oparent-master-release- > > version-java-daily/124/). Ultimately, the Docker manifest > > file<https://git.onap.org/integration/tree/version- > > manifest/src/main/resources/docker-manifest.csv?h=beijing> (In > > Beijing > > Branch) should not contain words such as “latest”, “SNAPSHOT” or > > “STAGING” but only version number. If necessary, also update the > > Java > > manifest file. All the release process is documented in > > wiki<https://wiki.onap.org/display/DW/Independent+Versioning+and+Release+Process>. > > > > 2. Release Notes: I have updated for most projects the > > “Security > > Notes” within each Release Notes. Thanks to review and merge its > > content (feel free to amend to fix typo, if any). Also, it is not > > necessary to list in the Release Notes all issues fixed into Beijing > > Release, but only the main one that were visible in Amsterdam > > externally to users. Same approach for “New Features”, it is not > > necessary to list all Jira Stories implemented in Beijing, but > > rather > > focus on describing the 3-4 main features of your project. Last, > > Release Notes are cumulative (all release notes go in a single > > file); > > information for Beijing Release goes on the top of the file. > > > > 3. Release Sign-Off Template: The Release Sign-Off template is > > available in > > wiki<https://wiki.onap.org/display/DW/Deliverables+for+Release+Sign- > > Off+Milestone+Checklist+Template>. Please fill it out and keep me > > posted on its availability so I can review. > > Let me know if you have question, I will be glad to help. > > Thanks, > > Gildas > > > > [HuaweiLogowithName] > > Gildas Lanilis > > ONAP Release Manager > > Santa Clara CA, USA > > [email protected]<mailto:[email protected]> > > Mobile: 1 415 238 6287 > > > > > > > > > > > _______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
