Created by Chaker Al-Hakim on September 26, 2019
Task Force Documentations
Topic | Link | |
---|---|---|
Initial Proposal - draft | Release Cadence Task ForceONAP Release Cadence task force, initial proposal - Oct 2019.pptx |
Objectives
Kickoff notes/thoughts:
- This task force will review the current release schedule and will make recommendations to the TSC on potential improvements to the current release schedule/cadence
- It is assumed that this effort will last for approximately 6 weeks after which an agreed to set of recommendation would be officially presented to the community
- the list of the team members is based on the members that volunteered to participate in this discuss. Please feel free to add your name to the list if you'd like to join or if i missed adding you to the list
- I have put together a draft proposal which was shared at high level on the Oct 7, 2019 PTL call. The draft will be attached to this page for everyone to review. This proposal is only meant as a starting point of our weekly discussions.
- I foresee this effort becoming an annual event where this task force would review all the releases (major, minor, etc..) and would 'tweak' the process based on members feedback and lessons learned.
Task Force Weekly Meeting Info
Start Date | End Date | |||
When | Every Wednesday | Oct 16, 2019 | Nov 20, 2019 | |
Time | 12:00pm (noon) EDT | |||
Zoom | https://zoom.us/j/240041076 |
Date | Oct. 23, 2019 | ||
---|---|---|---|
Attendees | |||
Recording | The audio recording is unavailable | ||
Action Items |
Date | Oct. 30, 3019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | Frankfurt Release
| ||
Action Items | |||
Recording | Oct 30, 2019 ONAP Release Cadence Recording.mp4 |
Date | Nov 6, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording | Nov 06, 2019 ONAP Release Cadence Recording |
Date | Nov 13, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording |
Date | Nov 20, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording |
Date | Nov 27, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording |
Date | Dec 4, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording |
Date | Dec 11, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording |
Date | Dec 18, 2019 | ||
---|---|---|---|
Attendees | |||
Agenda Topics | |||
Action Items | |||
Recording |
11 Comments
Liam Fallon
Chaker Al-Hakim I guess we start on October 16th (Wednesday) at 15:00 UTC rather than October 15th (Tuesday)?
Chaker Al-Hakim
Good catch, thank you Liam. page updated.
Vijay Venkatesh Kumar
@Chaker Al-Hakim - Will be good to also include the implication to branching/tagging along with release cadence proposed. Currently master branch is primarily used for ci flow/integration/delivery (rls branch are cut late in the cycle). For overlapping release schedules, it will be important to identify the target branch/process upfront.
Krzysztof Opasiak
Chaker Al-Hakim Thank you for putting together the slides.
Couple of suggestions from my side:
1) How we define a "stable" release?
2) How long are we going to support the stable release?
3) Are we going to provide any fixes (especially security) to the minor releases? If yes, then for how long
Chaker Al-Hakim
Krzysztof Opasiak Good comments. I will add them to the presentation as topics for discussion
Chaker Al-Hakim
Vijay Venkatesh Kumar - Good comments, will add them as well
Liam Fallon
Chaker Al-Hakim I can't make today's meeting due to a conflict.
Krzysztof Opasiak
Chaker Al-Hakim
How about keeping the meeting time in UTC to avoid confusion across different time zones?
Liam Fallon
I agree, we have two DST changes these two weekends, having meeting times in UTC means people only have to track DST changes in their own time zone and not DST changes in other time zones.
Liam Fallon
Chaker Al-Hakim Would it be possible for you to clarify the time of this week's meeting? The last call to meeting that you distributed on onap-discuss seemed to have a time of 23:00 UTC. At the moment my local time zone is the same as UTC.
Timo Perala
+1
For me the invite appears 1am on Wed. I believe this is not the intended starting time for the call. Also, at the top of this page it refers to "EDT", which together with DST ending and with the announcement of moving the call "up by one hour" makes it too complicated for me to calculate what is the true starting time of call![(wink)](/s/z10khv/8804/xgjkrn/_/images/icons/emoticons/wink.svg)
+1 to Krzystof's proposal, too.