Hi Emilien,

I'd love to take this role!
I have some tempest experience but not QA work which you mentioned
(devstack, grenade, zuul layout) that much. However, I think it will
be a very good opportunity to step-up.

So, for me, the next step might be to know grenade / upgrade jobs /
plugin mechanizm deeply. And I suppose we need some documentation
about "how to support upgrade" based on the requirements for the other
projects (and me :).

Any suggestion and/or comments are welcome!

-- Masayuki


On 01/11, Emilien Macchi wrote:
> Some projects are still not testing cold upgrades and therefore don't
> have the "supports-upgrade" tag.
> 
> https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html
> 
> This goal would mostly benefit the operators community as we would
> continue to ensure OpenStack can be upgraded and it's something that
> we actually test in the gate.
> In term of actions, we would need to run grenade / upgrade jobs for
> the projects which don't have this tag yet, so it's mostly QA work
> (devstack, grenade, zuul layout).
> 
> We're now looking for someone willing to lead this effort. Someone
> with a little bit of experience on QA and upgrades would work.
> However, our community is strong and we always help each others so no
> big deal if someone volunteers without all knowledge.
> A Champion is someone who coordinates the work to make a goal happen,
> and not supposed to do all the work. The Champion gets support from
> the whole community at any time.
> 
> Please step-up if you're willing to take this role!
> 
> Thanks,
> -- 
> Emilien Macchi
> 
> __________________________________________________________________________
> 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

Attachment: signature.asc
Description: PGP 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

Reply via email to