Unless you've been hiding under a rock (which is totally
understandable), you know that Zuul v3 is here.

Zuul v3 can be seen as a hindrance as of late because it's been
messing up with the gate jobs or preventing your patches to merge,
etc.
Hopefully, the "legacy" Zuul v3 jobs are all fixed up now and things
are able to merge without too much troubles.
I'm here to tell you that Zuul v3 is in fact awesome and I'd like
TripleO to benefit from all it's glory ASAP.

I encourage everyone, not just people typically involved in CI, to
take a read at the Zuul v3 migration guide 1.
Zuul v3 opens a lot of opportunities to streamline, improve and
simplify the CI of TripleO in upstream.

I'd like to open up an informal "ask me anything" regarding what's
implied in properly migrating TripleO jobs to "native" Zuul v3 and
have set up an etherpad to start collecting questions 2.
We could do a recorded Bluejeans session sometime early next week.
I've set up a Doodle, please tell us what time would work best for you 3.

Paul Belanger and I will be there to answer questions from a Zuul v3
and upstream infrastructure perspective.

We might also have questions for you !
For example, how do we plan on keeping jobs "compatible" between
review.openstack.org and review.rdoproject.org ?

Unless you've been hiding under a rock (which is totally
understandable), you know that Zuul v3 is here.

Zuul v3 can be seen as a hindrance as of late because it's been
messing up with the gate jobs or preventing your patches to merge,
etc.
Hopefully, the "legacy" Zuul v3 jobs are all fixed up now and things
are able to merge without too much troubles.
I'm here to tell you that Zuul v3 is in fact awesome and I'd like
TripleO to benefit from all it's glory ASAP.

I encourage everyone, not just people typically involved in CI, to
take a read at the Zuul v3 migration guide [1].
Zuul v3 opens a lot of opportunities to streamline, improve and
simplify the CI of TripleO in upstream.

I'd like to open up an informal "ask me anything" regarding what's
implied in properly migrating TripleO jobs to "native" Zuul v3 and
have set up an etherpad to start collecting questions [2].
We could do a recorded Bluejeans session sometime early next week.
I've set up a Doodle, please tell us what time would work best for you [3].

Paul Belanger and I will be there to answer questions from a Zuul v3
and upstream infrastructure perspective.

We might also have questions for you !
For example, how do we plan on keeping jobs "compatible" between
review.openstack.org and review.rdoproject.org ?

Unless you've been hiding under a rock (which is totally
understandable), you know that Zuul v3 is here.

Zuul v3 can be seen as a hindrance as of late because it's been
messing up with the gate jobs or preventing your patches to merge,
etc.
Hopefully, the "legacy" Zuul v3 jobs are all fixed up now and things
are able to merge without too much troubles.
I'm here to tell you that Zuul v3 is in fact awesome and I'd like
TripleO to benefit from all it's glory ASAP.

I encourage everyone, not just people typically involved in CI, to
take a read at the Zuul v3 migration guide 1.
Zuul v3 opens a lot of opportunities to streamline, improve and
simplify the CI of TripleO in upstream.

I'd like to open up an informal "ask me anything" regarding what's
implied in properly migrating TripleO jobs to "native" Zuul v3 and
have set up an etherpad to start collecting questions 2.
We could do a recorded Bluejeans session sometime early next week.
I've set up a Doodle, please tell us what time would work best for you [3].

Paul Belanger and I will be there to answer questions from a Zuul v3
and upstream infrastructure perspective.

We might also have questions for you !
For example, how do we plan on keeping jobs "compatible" between
review.openstack.org and review.rdoproject.org ?

On Mon, Oct 16, 2017 at 11:08 AM, David Moreau Simard <dms@redhat.com> wrote:
> Hi,
>
> Unless you've been hiding under a rock (which is totally
> understandable), you know that Zuul v3 is here.
>
> Zuul v3 can be seen as a hindrance as of late because it's been
> messing up with the gate jobs or preventing your patches to merge,
> etc.
> Hopefully, the "legacy" Zuul v3 jobs are all fixed up now and things
> are able to merge without too much troubles.
> I'm here to tell you that Zuul v3 is in fact awesome and I'd like
> TripleO to benefit from all it's glory ASAP.
>
> I encourage everyone, not just people typically involved in CI, to
> take a read at the Zuul v3 migration guide [1].
> Zuul v3 opens a lot of opportunities to streamline, improve and
> simplify the CI of TripleO in upstream.
>
> I'd like to open up an informal "ask me anything" regarding what's
> implied in properly migrating TripleO jobs to "native" Zuul v3 and
> have set up an etherpad to start collecting questions [2].
> We could do a recorded Bluejeans session sometime early next week.
> I've set up a Doodle, please tell us what time would work best for you [3].
>
> Paul Belanger and I will be there to answer questions from a Zuul v3
> and upstream infrastructure perspective.
>
> We might also have questions for you !
> For example, how do we plan on keeping jobs "compatible" between
> review.openstack.org and review.rdoproject.org ?
>
> Thanks !
>
> [1]: https://docs.openstack.org/infra/manual/zuulv3.html
> [2]: https://etherpad.openstack.org/p/migrating-tripleo-zuulv3
> [3]: https://doodle.com/poll/hfkcgrahwskm2ggv
>
> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]

Unless you've been hiding under a rock (which is totally
understandable), you know that Zuul v3 is here.

Zuul v3 can be seen as a hindrance as of late because it's been
messing up with the gate jobs or preventing your patches to merge,
etc.
Hopefully, the "legacy" Zuul v3 jobs are all fixed up now and things
are able to merge without too much troubles.
I'm here to tell you that Zuul v3 is in fact awesome and I'd like
TripleO to benefit from all it's glory ASAP.

I encourage everyone, not just people typically involved in CI, to
take a read at the Zuul v3 migration guide [1].
Zuul v3 opens a lot of opportunities to streamline, improve and
simplify the CI of TripleO in upstream.

I'd like to open up an informal "ask me anything" regarding what's
implied in properly migrating TripleO jobs to "native" Zuul v3 and
have set up an etherpad to start collecting questions [2].
We could do a recorded Bluejeans session sometime early next week.
I've set up a Doodle, please tell us what time would work best for you
[3].

Paul Belanger and I will be there to answer questions from a Zuul v3
and upstream infrastructure perspective.

We might also have questions for you !
For example, how do we plan on keeping jobs "compatible" between
review.openstack.org and review.rdoproject.org ?

On Mon, Oct 16, 2017 at 11:08 AM, David Moreau Simard <dms@redhat.com> wrote:
> Hi,
>
> Unless you've been hiding under a rock (which is totally
> understandable), you know that Zuul v3 is here.
>
> Zuul v3 can be seen as a hindrance as of late because it's been
> messing up with the gate jobs or preventing your patches to merge,
> etc.
> Hopefully, the "legacy" Zuul v3 jobs are all fixed up now and things
> are able to merge without too much troubles.
> I'm here to tell you that Zuul v3 is in fact awesome and I'd like
> TripleO to benefit from all it's glory ASAP.
>
> I encourage everyone, not just people typically involved in CI, to
> take a read at the Zuul v3 migration guide [1].
> Zuul v3 opens a lot of opportunities to streamline, improve and
> simplify the CI of TripleO in upstream.
>
> I'd like to open up an informal "ask me anything" regarding what's
> implied in properly migrating TripleO jobs to "native" Zuul v3 and
> have set up an etherpad to start collecting questions [2].
> We could do a recorded Bluejeans session sometime early next week.
> I've set up a Doodle, please tell us what time would work best for you [3].
>
> Paul Belanger and I will be there to answer questions from a Zuul v3
> and upstream infrastructure perspective.
>
> We might also have questions for you !
> For example, how do we plan on keeping jobs "compatible" between
> review.openstack.org and review.rdoproject.org ?
>
> Thanks !
>
> [1]: https://docs.openstack.org/infra/manual/zuulv3.html
> [2]: https://etherpad.openstack.org/p/migrating-tripleo-zuulv3
> [3]: https://doodle.com/poll/hfkcgrahwskm2ggv
>
> David Moreau Simard
> Senior Software Engineer | OpenStack RDO
>
> dmsimard = [irc, github, twitter]