PTL 2019-07-01
- Former user (Deleted)
- Tony Hansen
- Kenny Paul
zoom bridge: https://zoom.us/j/283628617
Duration 60 minutes
| Duration | Agenda Item | Requested by | Notes / Links |
|---|---|---|---|
| START RECORDING | |||
| 10min | Dublin | Sign-Off Vote in progress with the TSC - Congratulations to all of you - Thank you for your hard work ! Please continue to clean-up JIRA Dublin tickets - 369 items
Action(s): -Can we close the tickets in "Delivered" State? -Security status (OSJI ) i.e. Fix Accepted, Not a security Bug, public Disclosure, Confirmed - what's the termination status? How can we move forward? -Open/In Progress/Re Opened/New should move to El-Alto or Frankfurt or blank Fixed Release -Review "Submitted" if the code has been merged then can we close it? If the code was not merged then move to "El-Alto or Frankfurt or blank Fixed Release" JIRA Query status != Closed AND status != Done AND project != "Sandbox Project" AND project != CI-Management AND project != "ONAP TSC" and fixVersion = "Dublin Release" ORDER BY key ASC, priority DESC, updated DESC
| |
| 30min | El Alto plans review | PTLs to identify their El-Alto JIRA Tickets based on TSC "Must Have" by June 24th, 2019. TSC to review the "El Alto release" content on June 27 Content of El-Alto Early Drop When PTL is ready then add the JIRA query on the wiki page - Project Status in El-Alto Release
Please note we have already 34 Highest/High Bugs
Please note 47 Documentation Items
Full content of El-Alto Release 1717 items where (affectedversion = “El Alto Release” OR fixVersion = "El Alto Release")
Action(s): -Can we close the tickets in "Delivered" State? -Security status (OSJI ) i.e. Fix Accepted, Not a security Bug, public Disclosure, Confirmed - what's the termination status? How can we move forward? -Review "Submitted" if the code has been merged then can move them to "Delivered" for testing -Can we review "Open/In Progress" - have we really the intention to deliver them over the next 2 months+? Jira Query status not in (Closed,Done) AND project not in (CI-Management, "Sandbox Project", "ONAP TSC") AND (affectedVersion = "El Alto Release" OR fixVersion = "El Alto Release") ORDER BY priority DESC | |
| Global-jjb | Deadline July 19th global-jjb Migration Tracker | ||
| Windriver Lab Capacity update | |||
| 15min | CII Badging in El Alto | Tony Hansen | |
| 10min | OJSIs status update | The goal is to present to the community progress on OJSIs jiras that are related to penetration tests results. It is great that some projects already started their work, but some others (majority) not really. As clock is ticking - deadline to submit fixes is 27th of July - after this date it might be that some projects would have to review their scoring in CII Badging. If any support from SECCOM is required, please don't hesitate to come back to us - we are here to help you! | |
| Discuss the PTL JIRA restriction request | Summary of issues related to release version / fix version | ||
| LFS Staff Survey | Kenny Paul | https://www.surveymonkey.com/r/PT68D3Q | |
Zoom Chat Log
07:03:21 From Catherine Lefevre : https://onap.readthedocs.io/en/dublin/release/index.html#how-to-report-a-bug
07:03:41 From Catherine Lefevre : https://lf-onap.atlassian.net/wiki/display/DW/Tracking+Issues+with+JIRA#TrackingIssueswithJIRA-RecommendationsforwrittingProperJIRAIssue
07:04:16 From Keong : the recommendation should probably be to use onap-discuss mailing list first
07:05:04 From Jim Baker (LFN) : https://www.surveymonkey.com/r/PT68D3Q
07:05:51 From Catherine Lefevre : @seshu - did you complete the action item - take the the geographic support issue with the openlab-sub ?
07:06:35 From Tony Hansen : thank you for re-enabling Zoom’s Call Me option
Action Items
- Krzysztof Kuzmicki , Former user (Deleted) - Review OSJI ticket status in order to remove JIRA status that we should not track i.e. Not a Security Bug, Public Disclosure etc + define a way to report status dynamically
- cl664y@att.com - discuss with the TSC if they would like to proceed with OSJI tickets like we handle the Legal issues
- cl664y@att.com - send a note to onap-release, onap-security to clarify 60 Days CVE expectations and collect feedback
- Former user (Deleted) - review - Tracking Issues with JIRA#RecommendationsforwrittingProperJIRAIssue to ensure we are not suggesting people to fill in FixVersion field? <Reviewed the procedures listed on the wiki - text reads: Fix Version/s: Project version(s) for which the issue is (or was) fixed or a story is delivered. It does not suggest using fixVersion as rolling backlog tag. In the comments, Gildas recommends using the fixVersion tag to defer something for a future release.>
- Seshu Kumar Mudiganti take the the geographic support issue with the openlab-sub
- Leimeng Shi to discuss upgrades with the Portal meeting