On Wed, Feb 7, 2018 at 10:14 AM, Francesco Romani <fromani(a)redhat.com> wrote:
On 02/07/2018 08:46 AM, Dan Kenigsberg wrote:
> On Tue, Feb 6, 2018 at 10:28 PM, Francesco Romani <fromani(a)redhat.com> wrote:
>> Hi all,
>>
>>
>> With the help of Sandro (many thanks @sbonazzo !), we created minutes
>> ago the ovirt-4.2 stable branch:
>>
>>
>> Steps performed:
>>
>> 1. merged
https://gerrit.ovirt.org/#/c/87070/
>>
>> 2. branched out ovirt-4.2 from git master
>>
>> 3. merged
https://gerrit.ovirt.org/#/c/87181/ to add support for 4.3 level
>>
>> 4. createed and pushed the tag v4.30.0 from master, to make sure the
>> version number is greater of the stable versions, and to (somehow :))
>> align with oVirt versioning
>>
>> 5. tested make dist/make rpm on both new branch ovirt-4.2 and master,
>> both looks good and use the right version
>>
>>
>> Maintainers, please check it looks right for you before merging any new
>> patch to master branch.
>>
>>
>> Please let me know about any issue!
> Thank you Francesco (and Sandro).
>
> Any idea why
http://plain.resources.ovirt.org/pub/ovirt-4.2-snapshot/rpm/el7/noarch/
> still does not hold any vdsm-4.20 , and
>
http://plain.resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el7/noarch/
> does not have the new vdsm-4.30 ?
>
> ?
Uhm, maybe related to CQ (Change Queue), because git state looks ok, one
data point:
http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-on-demand-el7-x8...
built from this patch
https://gerrit.ovirt.org/#/c/87213/
in turn based on top of current master
Maybe Barak knows? Making GQ tick is the intention of the jenkins
patch, isn't it?