I really discourage having separated repos for specs, scripts or any 'code' used
for building any official packages.
That complicates (to the point of making it not feasible) a continuous build approach, and
introduces a lot of complexity and limitations to the continuous integration of the
If we can avoid it, I really discourage it. Can we talk about it and find a more friendly
On Jan 9, 2015 4:27 PM, Sandro Bonazzola <sbonazzo(a)redhat.com> wrote:
Il 09/01/2015 15:13, Juan Hernández ha scritto:
> Please create the following new git repIl 09/01/2015 15:13, Juan Hernández ha
Please create the following new git repositories:
They will be used to manage the RPM spec files (also scripts, patches,
and in general anything needed for building RPMs) of the Python SDK, the
Java SDK, and the CLI. Each repository will have branches for each pair
of oVirt major release and supported distribution:
Any reason for not having something like "ovirt-specs"
with suggested branches:
and having there
Initially I will be the maintainer of these repositories.
Once these repos are created the specs will be added to them and
eventually removed completely from the main repositories of the SDKs and
Thanks in advance,
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
Infra mailing list