[openstack-dev] [TC] Stein Goal Selection

Rico Lin rico.lin.guanyu at gmail.com
Fri Jun 8 07:40:28 UTC 2018


Kendall Nelson <kennelson11 at gmail.com> 於 2018年6月8日 週五 上午4:26寫道:
>
> I think that these two goals definitely fit the criteria we discussed in
Vancouver during the S Release Goal Forum Session. I know Storyboard
Migration was also mentioned after I had to dip out to another session so I
wanted to follow up on that.
>
+1. To migrate to StoryBoard do seems like a good way to go.
Heat just moved to StoryBoard, so there is no much long-term running
experiences to share about, but it does look like a good way to target the
piece which we been missing of. A workflow to connect users, ops, and
developers (within Launchpad, we only care about bugs, and what generate
that bug? well...we don't care). With Story + Task-oriented things can
change (To me this is shiny).

For migrate experience, the migration is quick, so if there is no project
really really only can survive with Launchpad, I think there is no blocker
for this goal.

Also, it's quite convenient to target your story with your old bug, since
your story id is your bug id.

Since it might be difficult for all project directly migrated to it, IMO we
should at least have a potential goal for T release (or a long-term goal
for Stein?). Or we can directly set this as a Stein goal as well. Why?
Because of the very first Story ID actually started from 2000000(and as I
mentioned, after migrating, your story id is exactly your bug id ). So once
we generate bug with ID 2000000, things will become interesting (and hard
to migrate). Current is 1775759, so one or two years I guess?

To interpreted `might be difficult` above, The overall experience is great,
some small things should get improve:

   - I can't tell if current story is already reported or not. There is no
   way to filter stories and checking conflict if there is.
   - Things going slow if we try to use Board in StoryBoard to filter out a
   great number of stories (like when I need to see all `High Priority` tagged
   stories)
   - Needs better documentation, In Heat we create an Etherpad to describe
   and collect Q&A on how people can better adopt StoryBoard. It will be great
   if teams can directly get this information.

Overall, I think this is a nice goal, and it's actually painless to migrate.


--
May The Force of OpenStack Be With You,
Rico Lin
irc: ricolin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180608/8dd99cb8/attachment.html>


More information about the OpenStack-dev mailing list