PTL 2020-05-04
- David McBride
- cl664y@att.com
- Morgan Richomme
Agenda
START RECORDING
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| 1 hour | Cross-project discussions OOM evolution for Guilin and consequences on the projects Integration evolution for Guiling and consequences for the projects | ||
LF IT Support |
| ||
| Testing Environment | |||
Testing Improvement | |||
CSIT Review | |||
ToolChain Improvement | |||
| Documentation | Update doc migration - https://gerrit.onap.org/r/c/doc/+/105796/8 Migration tracking page: https://lf-onap.atlassian.net/wiki/x/tVz6 | ||
Other Improvement suggestion | |||
Subcommittee Updates for PTLs | |||
Sharing Best Practices | |||
| IF TIME ALLOWS .... | |||
| 15 mins | Release status |
| |
| 5 mins | Upcoming Events |
| |
| 10 mins | Remaining Action Items | ||
Zoom Chat Log
06:08:54 From Kenny Paul (LFN) : Please remember to create your meetings on the calendar: https://lists.onap.org/g/onap-ptl/message/46
06:09:33 From Kenny Paul (LFN) : #topic Guilin integration
06:25:13 From Dan Timoney : Note: by way of comparison, OpenDaylight only releases at major milestones ... so build version always tells you whether it is the initial release (x.y.0), or a service release (x.y.{service release #})
06:29:46 From Pamela Dragosh : This is great and I agree - but it doesn’t match with the way we do Release Cadence. We need to change that laborious and time consuming process.
06:30:51 From Krzysztof Opasiak : Fully agree with Pam. We even put together a new release cadence proposal and presented it in Prague but for some unknown for me reason it died.
06:31:04 From Krzysztof Opasiak : @Chaker any chance to push this proposal forward?
06:31:45 From John Franey : Probably, the gerrit branch restriction may not support multiple releases. Scenario: 1) release last week, 2) more progress on master, 3) last week's release has a bug...where to put fix for last weeks release?
06:33:39 From Jimmy Forsyth : Mulitple interpedent repos take a long time to release with the current process - it's not labor intensive but it is a lot of waiting
06:35:20 From Pamela Dragosh : What gerrit branch restriction?
06:39:51 From John Franey : each onap individual project can have only a development branch, and an onap release branch for fixing release (e.g, Frankfurt). Other branches are not allowed. For example, the case where a project does releases frequently within an onap grand release.
06:41:12 From Pamela Dragosh : I’ve been on ONAP since its inception, never heard of that. Of course, I’ve never needed that. We’re able to manage bug fixes on each release branch and have no need of yet another branch.
06:42:53 From John Franey : my question is really how a project can manage multiple intermediate releases under the proposal.
06:43:15 From John Franey : ...inabsence of fluent branching.
06:57:04 From Kenny Paul (LFN) : dropping now.