[release] [Reminder #4] Oxygen M2 Project Status Due


Yi-Ling Hsieh
 

Hi Kit,

 

I’m the committer of the OpenDaylight SNMP4SDN project, but now I can’t login https://git.opendaylight.org now so that I can’t submit the M2 status report. Who can I ask for help, please?

(I have an account in https://identity.linuxfoundation.org/, the username/password also works for https://wiki.opendaylight.org, but fails for https://git.opendaylight.org )

 

Thanks!

Best regards,

Christine

 

 

 

 

From: release-bounces@... [mailto:release-bounces@...] On Behalf Of Kit Lou
Sent: Tuesday, December 12, 2017 6:14 AM
To: dlux-dev@...; dluxapps@...; eman-dev@...; faas-dev@...; jsonrpc-dev@...; mdsal-dev@...; netconf-dev@...; of-config-dev@...; p4plugin-dev@...; snmp4sdn-dev@...; unimgr-dev@...; yangtools-dev@...
Cc: Release
Subject: [release] [Reminder #4] Oxygen M2 Project Status Due

 

Hello Oxygen Projects,

 

For the projects (details below) that have submitted M2 project status  - thank you!

 

We are still waiting for Oxygen M2 Project Status from the 12 following projects: dlux, dluxapps, eman, faas, jsonrpc, mdsal, netconf, of-config, p4plugin, snmp4sdn, unimgr, yangtools

 

We request that these 12 projects submit their M2 status as soon as possible!

 

Instructions: Please make a copy of the m2 status template file [1], update, and submit your milestone readout into this folder of the docs project:  "docs/release-process/milestone-readouts/m2".

 

There is a useful online reStructuredText tool [2] you can use to validate your rst file contents - copy the rst file contents into the left pane and you will see the rendered HTML on the right pane.  If your rst file checkin fails verification, it will likely be failing the tox coala check.  Please look for the tox-coala.log.gz file in the build log for details.

 

Note that once you submitted your gerrit patch and it is successfully merged, you will be able to see it here [3].

 

 

Best Regards,

Kit Lou

Release Manager



--
本信件可能包含工研院機密資訊,非指定之收件者,請勿使用或揭露本信件內容,並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.


Sam Hague <shague@...>
 

Open a ticket with the helpdesk@.... gerrit was upgraded and the credentials system also. Some users didn't map correctly.

On Thu, Dec 14, 2017 at 9:21 PM, <ylhsieh@...> wrote:

Hi Kit,

 

I’m the committer of the OpenDaylight SNMP4SDN project, but now I can’t login https://git.opendaylight.org now so that I can’t submit the M2 status report. Who can I ask for help, please?

(I have an account in https://identity.linuxfoundation.org/, the username/password also works for https://wiki.opendaylight.org, but fails for https://git.opendaylight.org )

 

Thanks!

Best regards,

Christine

 

 

 

 

From: release-bounces@lists.opendaylight.org [mailto:release-bounces@lists.opendaylight.org] On Behalf Of Kit Lou
Sent: Tuesday, December 12, 2017 6:14 AM
To: dlux-dev@....org; dluxapps@....org; eman-dev@....org; faas-dev@....org; jsonrpc-dev@lists.opendaylight.org; mdsal-dev@....org; netconf-dev@lists.opendaylight.org; of-config-dev@lists.opendaylight.org; p4plugin-dev@lists.opendaylight.org; snmp4sdn-dev@lists.opendaylight.org; unimgr-dev@....org; yangtools-dev@lists.opendaylight.org
Cc: Release
Subject: [release] [Reminder #4] Oxygen M2 Project Status Due

 

Hello Oxygen Projects,

 

For the projects (details below) that have submitted M2 project status  - thank you!

 

We are still waiting for Oxygen M2 Project Status from the 12 following projects: dlux, dluxapps, eman, faas, jsonrpc, mdsal, netconf, of-config, p4plugin, snmp4sdn, unimgr, yangtools

 

We request that these 12 projects submit their M2 status as soon as possible!

 

Instructions: Please make a copy of the m2 status template file [1], update, and submit your milestone readout into this folder of the docs project:  "docs/release-process/milestone-readouts/m2".

 

There is a useful online reStructuredText tool [2] you can use to validate your rst file contents - copy the rst file contents into the left pane and you will see the rendered HTML on the right pane.  If your rst file checkin fails verification, it will likely be failing the tox coala check.  Please look for the tox-coala.log.gz file in the build log for details.

 

Note that once you submitted your gerrit patch and it is successfully merged, you will be able to see it here [3].

 

 

Best Regards,

Kit Lou

Release Manager



--
本信件可能包含工研院機密資訊,非指定之收件者,請勿使用或揭露本信件內容,並請銷毀此信件。 This email may contain confidential information. Please do not use or disclose it in any way and delete it if you are not the intended recipient.

_______________________________________________
release mailing list
release@...
https://lists.opendaylight.org/mailman/listinfo/release