[Rdo-list] Reminder: RDO test day tomorrow

[David Moreau Simard]

Hi Matthias,

The timing was not very convenient but we try to schedule the test days
around a week after a milestone [1] has been hit.

With FOSDEM and Devconf so close to each other, this would've meant pushing
the test days at least another two weeks (now three weeks or more after
milestone).

I feel we got good participation regardless, especially on the RDO Manager
side. Our CI is really getting awesome coverage and is leaps and bounds
beyond what we had even for M1 and I will share an update on that topic in
a blog post soon.

[1]: http://docs.openstack.org/releases/schedules/mitaka.html

David Moreau Simard
Senior Software Engineer | Openstack RDO

dmsimard = [irc, github, twitter]
On Feb 1, 2016 2:47 AM, "Matthias Runge" <mrunge at redhat.com> wrote:

> On Tue, Jan 26, 2016 at 03:14:46PM -0500, Rich Bowen wrote:
> > A reminder that we'll be holding the RDO Mitaka 2 test day Tomorrow and
> > Thursday - January 27-28. Details, and test instructions, may be found
> > here: https://www.rdoproject.org/testday/mitaka/milestone2/
> >
> > I will be traveling tomorrow, so I request that folks be particularly
> > aware on #rdo, so that beginners and others new to RDO have the support
> > that they need when things go wrong.
>
> Thank you for the heads up here. Could we schedule the next test days
> at a time, where not so many of us are travelling? (End of January
> is FOSDEM, and there is devconf.cz the week after), between both is
> config management camp (just illustrating, quite a few of us are
> very busy these days and unable to support, if an issue happens.)
>
> Thank you,
> Matthias
> --
> Matthias Runge <mrunge at redhat.com>
>
> _______________________________________________
> Rdo-list mailing list
> Rdo-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rdo-list
>
> To unsubscribe: rdo-list-unsubscribe at redhat.com
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rdoproject.org/pipermail/dev/attachments/20160201/e6e4e8fd/attachment.html>