Istanbul: Lessons Learned

Cannot complete arch reviews by M2.  Should we increase the time between M1 and M2? Some other solution?

@David McBride 

Can we start arch reviews earlier? Limited by sign off for previous release.

Can we increase cadence of arch SC meetings for review period? Have additional meetings in other time zones?

Disconnect between arch reviews and release management processes.  Example:  DMAAP-1615

@David McBride 

Improve communication between arch SC, RM, and PTLs

Verify that release name string is updated in documentation (i.e., “honolulu” release documentation showed release as “guilin”)

@Thomas Kulik 

Add to existing release management task.  

New task for M2:  PTLs complete color-coding of view-per-component GR requirements by M2 in order to highlight resource issues, or other problems, as early as possible.

@cl664y@att.com 

Implemented for Jakarta

Remove OOM tasks from M3 and move them to M4, since OOM activities trail project code review activities.

@Sylvain Desbureaux 

Tasks moved for OOM for Jakarta

Testing task should happen after container delivery.  Move to RC? (Toine)

@Toine Siebelink 

David to review release management tasks and update timing between container delivery and testing as necessary.

Jira cleanup for projects should move to Sign Off

@Dan Timoney 

David to review release management tasks and update timing between container delivery and testing as necessary.

Need to resolve ongoing issues with unmaintained projects:  simple bug fixes; publication of documentation, etc.

@Amy Zwarico 

Ongoing dedicated meeting on Mondays to address these issues.

Problem at the front of the release with release management tasks for requirements owners.  Since requirements submission doesn’t end before M1, it’s possible for new requirements to be added AFTER the release management tasks have been added.  Difficult to track without a lot of manual effort.

@David McBride 

RM to monitor requirements added to the release through M2 and update release management tasks accordingly.

Could requirement owners send notification to the requirements SC mailing list?

Cutoff at M2 prevents project teams from evaluating support.

Lessons Learned for the Documentation Project

@Thomas Kulik 

Begin X-testing on release branch as soon as the branch is available

@David McBride 

PTL transition issue.  Unlikely to be a problem going forward.

Get legal assessment on release no later than M3

@Kenny Paul 

Will file support ticket with legal team immediately following M2.