Release Manager trainees for 10.5, 10.6, 10.7, 10.8

This is the current schedule for Release Management in the next 4 months:

|Release|Release Date|Release Manager (EMEA/APAC)| Release Manager (Americas)|Trainee (Americas)|Trainee (EMEA/APAC)| |------|------|------|------|-----|----|----| |10.6|March 22, 2018|@jameslopez|@rspeicher|Filipa Lacerda|Mayra Cabrera| |10.7|April 22, 2018|@jameslopez|@rspeicher|Filipa Lacerda|Mayra Cabrera| |10.8|May 22, 2018|@jameslopez|@rspeicher|Alessio Caiazza| Sarrah Vesselov| |10.9|June 22, 2018|Filipa Lacerda|Mayra Cabrera|Alessio Caiazza| Chris Peressini| |10.10|July 22, 2018|Alessio Caiazza| Chris Peressini|Constance Okoghenun| TBD|

As you can see, Release Trainees are still undecided.

We want to have trainees rotate in 2 month cycle. This means we are looking for 4 people total, 2 from EMEA/APAC, 2 from Americas.

You will be involved in Release process at a very exciting time. As a run up to the continuous deployment that will be available on GitLab.com in H2, the process changes are going to be introduced to speed up the process.

Our goal is to increase automation and do quality of life improvements in takeoff and release tools, as well as speeding up the releases.

Trainees will be involved in doing releases by helping out with each of the process steps. This will be a more of a hands on approach in comparison with the previous trainees.

As for the required time for the RM work, trainees won't be working full time on release. You will be asked periodically to take over a certain task which should not take you more than a couple of hours every week.

Team leads, if you have ideas on anyone who wants to volunteer, please propose in comments; @ayufan @timzallmann @andrewn @smcgivern . Also including @DouweM and @rymai but given that they are already giving RM's for 3 months, it would be unrealistic to expect them to add more resources.