Hi Jeremy, that is exactly the issue we were discussing. Sometimes the context is simply "a developer emailed the docs team to change this guide on line 23 from A to B." If the commit message has the necessary details about the change, could the Jira number be just an identifier? Or does having a Jira number send the message that a non-public system is being used? In the example above, the simple change is opened as a Jira ticket and then is copied into LP to be linked in the commit message. We were chatting about alternatives, because no one wants to update/track info in 2 systems if there's a more efficient method. Appreciate your input -- good to know someone reads the docs meeting notes 😊 thanks, Mary Camp Kelly Services Technical Writer | maryx.camp@intel.com -----Original Message----- From: Jeremy Stanley <fungi@yuggoth.org> Sent: Wednesday, June 9, 2021 9:19 PM To: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [docs] [meeting] Docs team notes 09-Jun-21 On 2021-06-10 00:33:26 +0000 (+0000), Camp, MaryX wrote: [...]
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.
I'm not Greg, but still curious. If a non-WR-employed contributor, aspiring contributor, user, et cetera is reviewing a change or looking at a commit in Git history which references a Jira ticket, how do they obtain the content of that ticket so they have proper context? Are those tickets publicly accessible? -- Jeremy Stanley