Hi, despite CI freeze for substantial change is in order, I recognize there's always the need to add or modify slightly the jobs for important fixes or to improve debugging.
Unfortunately in these days we are wrapping up the gap in feature coverage between tripleo-ci and quickstart, and any of those change is increasing the list of features to be added to the implementation, making the wrap a moving target. Also, I'm seen some more-than-minor changes merged in these days, and that is making this job even more difficult. For those reason, we're going to ask everybody, from this moment on, for every change proposed to tripleo-ci, to propose an equivalent change to quickstart, or, if it seems too difficult, to open a bug in quickstart, pointing at the change in tripleo-ci, with some explanation on why it's needed, if it's not already clear in the commit message. At the end of this week we're going to make the final cut to the list of features we're going to transition to quickstart. If a feature, a test, an improvement, a small fix is added in tripleo-ci without signaling quickstart in any way, the risk is that the change will go unnoticed, and will be lost in transition. thanks for your collaboration. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
