How to address the gap between WR Jira tickets and LP - Story/Task info, without having to replicate all the info in 2 systems. Is there a reason why we can't reference Jira numbers in the commit messages? This is a question for Greg.
For internal wind river types generating bugs on docs, we can remind people that if it is a problem that is in the upstream starlingx docs, that they should be generating a starlingx LP. And then ONLY use the LP; no internal WR JIRA would be created. If the internal WR JIRA is already created ... not sure we can do much other than duplicate the info in an LP. Greg. -----Original Message----- From: Camp, MaryX <maryx.camp@intel.com> Sent: Wednesday, June 9, 2021 8:33 PM To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [docs] [meeting] Docs team notes 09-Jun-21 [Please note: This e-mail is from an EXTERNAL e-mail address] Hello all, Here are this week's docs team meeting minutes (short form). Details in [2]. Join us if you have interest in StarlingX docs! We meet on Wednesdays 12:30 PST. [1] Call logistics: https://wiki.openstack.org/wiki/Starlingx/Meetings [2] Tracking Etherpad: https://etherpad.openstack.org/p/stx-documentation thanks, Mary Camp ========== 09-Jun-21 All -- reviews merged since last meeting: 22 All -- bug status -- 17 total - team agrees to defer all low priority LP until the upstreaming effort is completed. Status/questions/opens Several reviewers are pressing for changes in commit messages - ie, where is the task/story info, why are they so long? Unclear why they are invested in the commit messages. Do we need to push back on this? Create "template" for commit messages for future updates. Add to parking lot for retrospective. How to address the gap between WR Jira tickets and LP - Story/Task info, without having to replicate all the info in 2 systems. Is there a reason why we can't reference Jira numbers in the commit messages? This is a question for Greg. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss