Good morning Bill, As discussed during the ONAP TSC on Sept 22nd, there is no official Jakarta Maintenance release. Nevertheless nothing prevents the AAI Project to provide a self-maintenance release if you are supported by the AAI committers/contributors. You will also check with the OOM team to merge changes; update the AAI release note And ensure that no use case is impacted by the new code. Ideally a run test performed by the Integration Team would also be appreciated.
Here is the ONAP Maintenance Policy for Project Release: Project Self-Release<https://wiki.onap.org/display/DW/Project+Self-Release> Best regards, Catherine From: [email protected] <[email protected]> On Behalf Of William Reehil Sent: Friday, September 16, 2022 9:22 PM To: [email protected] Subject: [onap-tsc] Jakarta Maintenance Request ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. Hi TSC, Bell Canada has requested to introduce enhancements to the Jakarta release branch, to my knowledge we do not have a J maintenance release. How should we handle this request? Thanks, William Reehil Principal Member of Technical Staff | A&AI ONAP PTL AT&T NETWORK SERVICES (C) 732 865-5333 | (O) 732 420-7806 -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#8949): https://lists.onap.org/g/onap-tsc/message/8949 Mute This Topic: https://lists.onap.org/mt/93730144/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-tsc/leave/2743226/21656/1412191262/xyzzy [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
