Good morning Ciaran, Thank you for your feedback.
We welcome any suggestion to reduce the time between M0 and M3. The current assumptions are that 1. Istanbul release might shift a little bit during the testing cycle 2. Project teams can hardly handle multiple releases at the same time (i.e. we are nearly there to complete Honolulu Maintenance after several months) 3. Critical developers/testers might take vacations or/and will be barely available from Nov 22nd until the second week of January 2022 4. A lot of events in January - DDF, Chinese Holiday, Epiphany, etc. Concerning your second request, Honolulu was the first prototype release for the new release cadence. Istanbul has been re-adjusted based on the lesson learned from Honolulu. Nothing prevents any project team from handling multiple releases at the same time, from self-releasing their project any time, from continuously developing and testing without breaking the gating, etc. The Jakarta milestones have indeed been defined to ensure that the ONAP Community will deliver a consolidated certified content at a certain moment. Nevertheless we are always open for any suggestion to improve the release cadence. Do you feel that you could work with David/PLTs in order to build a transformation plan in alignment with your expectations? Many thanks & regards, Catherine From: Ciaran Johnston <[email protected]> Sent: Thursday, September 30, 2021 1:04 AM To: [email protected]; Lefevre, Catherine <[email protected]> Cc: Magnus Buhrgard <[email protected]> Subject: Jakarta release schedule Hi TSC, Looking at the proposal for the Jakarta release schedule, we still seem to be following a relatively "waterfall" approach to project planning, which seems to somewhat go against the proposal for a new release cadence as agreed previously: https://wiki.onap.org/display/DW/Release+Cadence+Proposal?preview=/71835201/84657465/release%20cadence.pdf<https://urldefense.com/v3/__https:/wiki.onap.org/display/DW/Release*Cadence*Proposal?preview=*71835201*84657465*release*20cadence.pdf__;KysvLy8l!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJUYga8HLU$> Although perhaps it's just that the release schedule only indicates formal cut-off dates, but not the expectation on the development model during those dates. Before we vote to approve (or not) in the TSC meeting tomorrow, could we take a brief discussion on potential clarifications that could be made. Specifically, while there is a long period between M0 and M3 / M4, projects should be encouraged / expected to make regular small incremental deliveries into integration, to de-risk the chance of a big-bang approach impacting our timelines and individual's personal wellbeing towards the end of the project cycle. One proposal could be to introduce a specific, regular integration / release train approach, that individual projects are expected to regularly deliver into - something like this conceptually: [cid:[email protected]] This would mean - assuming most projects caught the train a few different times during the release period - any potential issues can be caught early, isolated and triaged before causing a bottleneck. Is this something we can discuss for inclusion in the release schedule? Thanks, Ciaran [http://mediabank.ericsson.net/internet-media/Email_logo_Ericsson.png]<https://urldefense.com/v3/__http:/www.ericsson.com/__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJU_xy5oYs$> Ciaran Johnston Expert Network Management Architecture OSS Chief Implementation Architect BDGS SA OSS PDU OSS S&T Phone: +353870997593 Mobile: +353870997593 [email protected]<mailto:[email protected]> Ericsson Ericsson Software Campus ,Athlone Ireland ericsson.com<https://urldefense.com/v3/__http:/www.ericsson.com/__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJU_xy5oYs$> [http://mediabank.ericsson.net/internet-media/Email_Message.gif]<https://urldefense.com/v3/__http:/www.ericsson.com/current_campaign__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJUet72l1U$> Our commitment to Technology for Good<https://urldefense.com/v3/__http:/www.ericsson.com/thecompany/sustainability-corporateresponsibility__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJUobn8TZs$> and Diversity and Inclusion<https://urldefense.com/v3/__http:/www.ericsson.com/thecompany/diversity-inclusion__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJU81Rst9I$> contributes to positive change. Follow us on: Facebook<https://urldefense.com/v3/__https:/www.facebook.com/ericsson__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJUWYN1uvE$> LinkedIn<https://urldefense.com/v3/__https:/www.linkedin.com/company/ericsson__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJU1HtIgds$> Twitter<https://urldefense.com/v3/__https:/twitter.com/Ericsson__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJUUvHBD5g$> Legal entity:L M ERICSSON LIMITED registration number , registered office in Dublin. This communication is confidential. Our email terms: www.ericsson.com/en/legal/privacy/email-disclaimer<https://urldefense.com/v3/__https:/www.ericsson.com/en/legal/privacy/email-disclaimer__;!!BhdT!yWJdLG0qgW0Hmxl8VL3IcvVxc1fS7hEFNmUoHCEiG-nZeIOz1qD5xRadALdL-ZJUFZHOE8k$> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8196): https://lists.onap.org/g/onap-tsc/message/8196 Mute This Topic: https://lists.onap.org/mt/85961999/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
