Open Stack

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 07/16/2015 05:08 PM, Thomas Goirand wrote:
> On 07/16/2015 03:29 PM, Ihar Hrachyshka wrote:
>> Working on upstream gate stability obviously does not invalidate
>> any effort to introduce distribution CI votes in gerrit, and I
>> would be happy to see RDO or Ubuntu meaningfully voting on
>> backports. It's my belief though that distribution CI votes
>> cannot serve as a replacement for upstream gate.
> 
> To me, it'd be a way more easy to work out a distribution CI
> *after* a release, than one following trunk. Following trunk is
> nuts, there's always the need for new packages and upgrade
> everything. Just like this week, upgrading python-taskflow made me
> try to: - upgrade mock - as a consequence setuptools - package 2 or
> 3 new 3rd party things - upgrade some other stuff
> 
> For a given release of OpenStack, things aren't moving, so it's
> easier to set it up. If the gate is always broken with upstream
> changes, distributions would not.
> 
> Also, having a CI which does build of packages on each commit, and
> the deployment + test of all that on a multi-node setup, is exactly
> what the Mirantis CI does. I'm not pretending it's easy to do (and
> in fact, it's not...), but at least, we do it for MOS, so it should
> be possible to do for the community version of OpenStack.
> 
> Let's hope we find the time to get this done.
> 

It would be great to see that one voting in upstream. And gate
working. And then there won't be particular reason to drop older branche
s.

Ihar
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJVp+T8AAoJEC5aWaUY1u57pWoIAL1pPBZSH6RPaseyhWVEsD4Q
1Y34kWZm27sgca6g10ycO1QxalBYb3X9wJzOhxezgajZaPFnRh0UJLwNqJgBAycO
eBGtBH5/FvBr3thWyjtO4thfyYoYdkbw1S5NwYmZ0hPspwXwMCBQh9yR2HDvy2N5
VXatm6yBQClbkyUnekhHxgi70wsVhQemWUzAGStCi7h45gpXC2+6NieDNFoXQkut
8rOcKFmU0i3AmHiyZGx7EbiuvT2Xwrsfu6x4bJeG9Ft3cWXjrHOGAGhqS23qcBBG
R34Q5LJvxJFKHgi89amaEF2tc89XRKxVPgHE4i4DGkJ44erozNrR74emF+imanI=
=ILdG
-----END PGP SIGNATURE-----