On Tue, Nov 7, 2017 at 6:45 PM, James E. Blair <[email protected]> wrote: > Erik McCormick <[email protected]> writes: > >> The concept, in general, is to create a new set of cores from these >> groups, and use 3rd party CI to validate patches. There are lots of >> details to be worked out yet, but our amazing UC (User Committee) will >> be begin working out the details. > > I regret that due to a conflict I was unable to attend this session. > Can you elaborate on why third-party CI would be necessary for this, > considering that upstream CI already exists on all active branches? > > Thanks, > > Jim
Lack of infra resources, people are already maintaining their own testing for old releases, and distribution of work across organizations I think were the chief reasons. Someone else feel free to chime in and expand on it. -Erik __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
