Re: [openstack-dev] [monasca][swift][storyboard] migration experience
On 2017-04-21 09:00:47 + (+), witold.be...@est.fujitsu.com wrote: > one thing which hasn't been migrated are the blueprints. We have > noticed this after the migration. Storyboard team has said they > had not planned on migrating blueprints because most of the > projects use the specs server. An option here might be to amend the migration script to also create new stories from open blueprints and add a story tag like "blueprint" to them. Part of the reason StoryBoard wasn't designed with a separate blueprint feature is that its story model is intended to be flexible enough to handle a lot of the same sorts of use cases for which blueprints were used (since unlike LP, you can have multiple tasks in a story for the same project without having to predefine a separate branch or series). But as you noted, the migration script didn't originally consider blueprints because there was a general trend within the community to move away from LP blueprints in favor of repos under code review where they could curate more detailed and structured specifications instead... so we weren't sure if anyone would still be using blueprints at all by the time we were ready to start on the majority migration. -- Jeremy Stanley __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [monasca][swift][storyboard] migration experience
> >2) Are you missing anything from the migration? How do you manage > >security bugs that are embargoed? Hi John, one thing which hasn't been migrated are the blueprints. We have noticed this after the migration. Storyboard team has said they had not planned on migrating blueprints because most of the projects use the specs server. Cheers Witek __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [monasca][swift][storyboard] migration experience
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" 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 > > > > > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [monasca][swift][storyboard] migration experience
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? 2) Are you missing anything from the migration? How do you manage security bugs that are embargoed? 3) How are you managing being "different" in the OpenStack community for where to go file bugs or track work? 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? 5) What other thoughts do you have on the move? Thank you for your time and thoughts, John signature.asc Description: OpenPGP digital signature __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
