Let's stick w/ one story we already have at this moment: https://storyboard.openstack.org/#!/story/2003389. I've already tagged as stx-distro.other. we need to target it at Oct's release, thus I am adding stx.2018.10 tag as well. Thx. - cindy -----Original Message----- From: Khalil, Ghada [mailto:Ghada.Khalil@windriver.com] Sent: Friday, August 10, 2018 4:13 AM To: Saul Wold <sgw@linux.intel.com>; Jones, Bruce E <bruce.e.jones@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] CentOS 7.5 upgrade discussion On 08/09/2018 11:44 AM, Khalil, Ghada wrote:
Hi Bruce, There is a story already for tracking the CentOS 7.5 upgrade. Shuicheng created it earlier (he's part of the Distro Non-Openstack team).
https://storyboard.openstack.org/#!/story/2003389
Dealing with the vim patch (i.e. removing it) should be a task under this story.
I thought we were doing 1 story / package, not 1 task / package? Can someone please clarify this, as I am also working on patches and they need stories or tasks. [[GK]] Sorry Saul I didn't know about this decision as I was not part of the discussion. I personally feel if work items can be logically combined into one story with multiple tasks, that would be beneficial. It's a way to avoid story explosion. That being said, in the end, it's up to you and the sub-project team. If it makes more sense to have a story/package, that's fine as well. PS: I am a bit biased as I have been trying to tag the backlog, so the less stories the better for me. But that's a short term issue as each sub-project starts to tag their own. Ghada _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss