[openstack-dev] [monasca][swift][storyboard] migration experience

Hochmuth, Roland M roland.hochmuth at hpe.com
Fri Apr 21 04:06:36 UTC 2017


Hi John, Comments in-line below. I'm hoping that someone else will add more details.




On 4/17/17, 2:50 PM, "John Dickinson" <me at not.mn> wrote:

>Moasca-teers
>
>As the migration away from Launchpad and to Storyboard moves forward,
>the Swift team has been considering making the move. Monasca has
>already made the move, so I'd love to hear your thoughts on that
>process.
>
>1) How did you do the change? All at once or gradually? If you did it
>over again, would you do it the same way?

[RH]: The change was done all at once and yes I would do it the same way. The migration went smoothly.
>
>2) Are you missing anything from the migration? How do you manage
>security bugs that are embargoed?

[RH]: It hasn't been very long since the change. I don't believe we've run into any issues other than folks getting used to it. For example, getting the story and task ID in the commit message.
>
>3) How are you managing being "different" in the OpenStack community
>for where to go file bugs or track work?

[RH]: It takes a bit of reminding as the old habits are hard to change. Since our community of developers is rather small we are able to track this. However, we have had some bugs get created in launchpad after the merge, which we'll need to migrate to storyboard. 
>
>4) Have you had any negative impact from old links to Launchpad bugs?
>What about links in commit messages? How did you manage links in
>patches that were open at the time of migration?

[RH]: It has been a little painful getting links in commit messages updated.
>
>5) What other thoughts do you have on the move?

[RH]: That is a good question. Maybe we should do a retrospective on this topic during our next meeting.
>
>Thank you for your time and thoughts,
>
>
>John
>
>
>
>
>


More information about the OpenStack-dev mailing list