On Wed, May 9, 2018 at 3:25 PM Alex Schultz <[email protected]> wrote:
> Hello tripleo folks, > > So we've been experimenting with migrating some squads over to > storyboard[0] but this seems to be causing more issues than perhaps > it's worth. Since the upstream community would like to standardize on > Storyboard at some point, I would propose that we do a cut over of all > the tripleo bugs/blueprints from Launchpad to Storyboard. > > In the irc meeting this week[1], I asked that the tripleo-ci team make > sure the existing scripts that we use to monitor bugs for CI support > Storyboard. I would consider this a prerequisite for the migration. > I am thinking it would be beneficial to get this done before or as > close to M2. > > Thoughts, concerns, etc? > Just clarifying. You would like to have the tooling updated by M2, which is fine I think. However squads are not expected to change all their existing procedures by M2 correct? I'm concerned about migrating our current kanban boards to storyboard by M2. Thanks > > Thanks, > -Alex > > [0] https://storyboard.openstack.org/#!/project_group/76 > [1] > http://eavesdrop.openstack.org/meetings/tripleo/2018/tripleo.2018-05-08-14.00.log.html#l-42 > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
