Open Stack

On Tue, Jan 3, 2017 at 4:04 PM, Harry Rybacki <hrybacki at redhat.com> wrote:
> Greetings All,
>
> Folks have been diligently working on the blueprint[1] to prepare
> TripleO-Quickstart (OOOQ)[2] and TripleO-Quickstart-Extras[3] for
> their transition into TripleO-CI. Presently, our aim is to begin the
> actual transition to OOOQ on 4-Feb-2017. We are tracking our work on
> the RDO-Infra Trello board[4] and holding public discussion of key
> blockers on the team’s scrum etherpad[5].
>
> We are hosting weekly transition update meetings (1600-1700 UTC) and
> would like to invite folks to participate. Specifically, we are
> looking for at least one stakeholder in the existing TripleO-CI to
> join us as we prepare to migrate OOOQ. Attend and map out job/feature
> coverage to identify any holes so we can begin plugging them. Please
> reply off-list or reach out to me (hrybacki) on IRC to be added to the
> transition meeting calendar invite.

Is there still an ongoing effort to move OVB based jobs to be 3rd party CI?

Based on the previous email threads about 3rd party CI[1] and the
discussions at summit, I was under the impression that we'd move to
3rd party CI first, as there seemed to be more urgency around that.
Then, we'd transition to quickstart. It sounds like we're going to
transition to quickstart first though.

That is fine, but as others have mentioned, I'd like to see the rate
of change controlled in the CI system, especially around release time.
I'm wondering if there are still plans to move to 3rd party and how
those plans might line up with this proposed schedule.

[1] http://lists.openstack.org/pipermail/openstack-dev/2016-October/105248.html

-- 
-- James Slagle
--