Hello all,

In StarlingX, we currently use labels for target releases for Features/Enhancements as well as bugs [0]:

Example: stx.2018.10 (October Release), stx.2019.03 (March Release).

 

For low priority bugs or enhancements which may not have a target release, I was thinking to use a specific tag to indicate that they do not gate any release – stx.ng or stx.notgating. This would help with the screening/prioritization process. Right now, we leave them blank (w/o a release tag), but it’s harder to tell if they have been reviewed or not. I like the idea of having an explicit release better.

 

Any thoughts or concerns?

 

[0] https://wiki.openstack.org/wiki/StarlingX/Tags_and_Prefixes

 

Thanks,

Ghada

 

 

From: Khalil, Ghada
Sent: Monday, September 17, 2018 6:23 PM
To: 'starlingx-discuss@lists.starlingx.io'
Subject: Bug Handling Process / Useful Launchpad Bugs / Focus on stx.2018.10 Bugs

 

Hello all,

I’ve documented details of the StarlingX Bug Handling process on the wiki:

https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process

 

Please review and let me know if you have any feedback. All feedback is welcome.

 

In the above wiki, I have included links to useful Launchpad bugs:

https://wiki.openstack.org/wiki/StarlingX/Defect_Handling_Process#Key_StarlingX_Bug_Queries

 

With the team’s focus on stx.2018.10, I have created specific queries for the release. Project Leads, Please have a look at the unassigned stx.2018.10 bugs and assign to the team accordingly. Please also track all stx.2018.10 bugs to resolution as part of your regular team meetings/communication.

 

Thanks,

Ghada

 

 

Ghada Khalil, Manager, Titanium Cloud, Wind River
direct 613.270.2273  skype ghada.khalil.ottawa

350 Terry Fox Drive, Suite 200, Kanata, ON K2K 2W5