Alex Schultz
2018-05-15 14:53:32 UTC
Bumping this up so folks can review this. It was mentioned in this
week's meeting that it would be a good idea for folks to take a look
at Storyboard to get familiar with it. The upstream docs have been
updated[0] to point to the differences when dealing with proposed
patches. Please take some time to review this and raise any
concerns/issues now.
Thanks,
-Alex
[0] https://docs.openstack.org/infra/manual/developers.html#development-workflow
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailma
week's meeting that it would be a good idea for folks to take a look
at Storyboard to get familiar with it. The upstream docs have been
updated[0] to point to the differences when dealing with proposed
patches. Please take some time to review this and raise any
concerns/issues now.
Thanks,
-Alex
[0] https://docs.openstack.org/infra/manual/developers.html#development-workflow
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?
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
__________________________________________________________________________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?
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: OpenStack-dev-***@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailma