On Thu, Jun 16, 2016 at 5:24 PM, Francesco Romani wrote:
> Hi all,
>
> it was recently pointed out that Vdsm 4.18.3 rpms have -0 release number,
> like in
>
> rpmbuild/RPMS/x86_64/vdsm-4.18.3-0.fc23.x86_64.rpm
>
> But this is OK only for packages built from master. From
Hi all,
it was recently pointed out that Vdsm 4.18.3 rpms have -0 release number, like
in
rpmbuild/RPMS/x86_64/vdsm-4.18.3-0.fc23.x86_64.rpm
But this is OK only for packages built from master. From stable branch and
official releases,
we should have something like
Hi everyone,
I think Sven was referring specifically to oVirt Dashboard component
of oVirt Engine product. Dashboard (UI plugin) has its own repo [1]
[1] https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard
with dedicated Jenkins job to build its RPM. When Engine is installed,
Hi,
first thanks for this in depth and long
explanation. I'm actually already aware
of what you just explained.
But I'm a long time user, I guess, so I had
plenty of time to get used to all this.
But you didn't factor in other important things
like: which datacenter or cluster version does
I'm not sure what you mean or which versions you're referring to.
Like every project there is the 'master' branch and nightlies which is
latest and greatest (and probably the least stable, but still go over heavy
CI tests).
The oVirt project reached a point when the next stable major version (4.0)
> On Jun 16, 2016, at 11:06 AM, Sven Kieske wrote:
>
> On 14/06/16 17:34, Vojtech Szocs wrote:
>> Hi,
>>
>> ovirt-engine-dashboard is currently built from master as well.
>>
>> We should probably create a stable branch, e.g. ovirt-engine-dashboard-1.0.
>
> Hi,
>
>
On 14/06/16 17:34, Vojtech Szocs wrote:
> Hi,
>
> ovirt-engine-dashboard is currently built from master as well.
>
> We should probably create a stable branch, e.g. ovirt-engine-dashboard-1.0.
Hi,
speaking as an end user (mostly):
please not yet-another-versioning in the great ovirt project.