Re: [onap-discuss] Beijing Release: Last Mile

[Jessica Wagantall]

*No request received yet also from the modeling team.*

Thanks!
Jess

On Tue, Jun 5, 2018 at 3:14 PM, Jessica Wagantall <
jwagant...@linuxfoundation.org> 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
> 
> 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 <
> jwagant...@linuxfoundation.org> 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
>> 
>> 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 > > 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
>>> 
>>> (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
>>> 
>>> .
>>>
>>> 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
>>> .
>>> 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
>>>
>>>
>>>
>>> *[image: HuaweiLogowithName]*
>>>
>>> *Gildas Lanilis*
>>>
>>> *ONAP Release Manager*
>>>
>>> *Santa Clara CA, USA*
>>>
>>> *gildas.lani...@huawei.com *
>>>
>>> *Mobile: 1 415 238 6287*
>>>
>>>
>>>
>>
>>
>

Re: [onap-discuss] Beijing Release: Last Mile

[Jessica Wagantall]

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

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 <
jwagant...@linuxfoundation.org> 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
> 
> 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 
> 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
>> 
>> (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
>> 
>> .
>>
>> 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
>> .
>> 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
>>
>>
>>
>> *[image: HuaweiLogowithName]*
>>
>> *Gildas Lanilis*
>>
>> *ONAP Release Manager*
>>
>> *Santa Clara CA, USA*
>>
>> *gildas.lani...@huawei.com *
>>
>> *Mobile: 1 415 238 6287*
>>
>>
>>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] Beijing Release: Last Mile

[Jessica Wagantall]

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

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 
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
> 
> (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
> 
> .
>
> 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
> .
> 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
>
>
>
> *[image: HuaweiLogowithName]*
>
> *Gildas Lanilis*
>
> *ONAP Release Manager*
>
> *Santa Clara CA, USA*
>
> *gildas.lani...@huawei.com *
>
> *Mobile: 1 415 238 6287*
>
>
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Beijing Release: Last Mile

[Gildas Lanilis]

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
 (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.

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.
 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
gildas.lani...@huawei.com
Mobile: 1 415 238 6287

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss