[Starlingx-discuss] stx-specs git repo directory structure
Hi, In the "stx-specs" git repo [1] the directory structure currently looks like "specs/approved". That's fine for this release, but once we get to next release we're going to have "old" specs still in there making it hard to keep track of which spec is for which release. I'm wondering whether we want to add a release-specific subdirectory like other OpenStack projects have. So specs being submitted now would go into "specs/2019.3/approved". Thanks, Chris [1] https://github.com/openstack/stx-specs
On Mon, Oct 15, 2018 at 11:27 AM Chris Friesen <chris.friesen@windriver.com> wrote:
I'm wondering whether we want to add a release-specific subdirectory like other OpenStack projects have. So specs being submitted now would go into "specs/2019.3/approved".
Yes we should do that, probably sooner than later if we want to be able to deep-link to them after they are approved. It looks like there are 5 in the queue right now, anyone care either way if we wait for those to be approved or cause them all to need a rebase? dt -- Dean Troyer dtroyer@gmail.com
Looks like 1 is merged already and 6 are in the queue. I think we can let the commit to create the 2019.03 directory merge first and ask the 6 people with outstanding specs to rebase. Chris - as part of your commit to create the 2019.03 directory can you also move the one spec that already merged into the new 2019.03 directory? Frank -----Original Message----- From: Dean Troyer [mailto:dtroyer@gmail.com] Sent: Monday, October 15, 2018 1:46 PM To: Friesen, Chris Cc: starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] stx-specs git repo directory structure On Mon, Oct 15, 2018 at 11:27 AM Chris Friesen <chris.friesen@windriver.com> wrote:
I'm wondering whether we want to add a release-specific subdirectory like other OpenStack projects have. So specs being submitted now would go into "specs/2019.3/approved".
Yes we should do that, probably sooner than later if we want to be able to deep-link to them after they are approved. It looks like there are 5 in the queue right now, anyone care either way if we wait for those to be approved or cause them all to need a rebase? dt -- Dean Troyer dtroyer@gmail.com _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
On 10/15/2018 11:50 AM, Miller, Frank wrote:
Looks like 1 is merged already and 6 are in the queue. I think we can let the commit to create the 2019.03 directory merge first and ask the 6 people with outstanding specs to rebase.
Chris - as part of your commit to create the 2019.03 directory can you also move the one spec that already merged into the new 2019.03 directory?
Done. In case anyone is interested, review is at: https://review.openstack.org/#/c/610669 Chris
participants (3)
-
Chris Friesen
-
Dean Troyer
-
Miller, Frank