[ovirt-devel] [ovirt-users] [ANN] oVirt 3.5.0 Second Beta is now available for testing

Thu Jul 24 09:06:44 UTC 2014

Il 24/07/2014 08:45, Alon Bar-Lev ha scritto:
> 
> 
> ----- Original Message -----
>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>> To: "Alon Bar-Lev" <alonbl at redhat.com>
>> Cc: devel at ovirt.org
>> Sent: Thursday, July 24, 2014 9:42:05 AM
>> Subject: Re: [ovirt-users] [ANN] oVirt 3.5.0 Second Beta is now available for	testing
>>
>> Il 23/07/2014 18:49, Alon Bar-Lev ha scritto:
>>>
>>>
>>> ----- Original Message -----
>>>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>>>> To: "Alon Bar-Lev" <alonbl at redhat.com>
>>>> Cc: devel at ovirt.org
>>>> Sent: Wednesday, July 23, 2014 7:07:22 PM
>>>> Subject: Re: [ovirt-users] [ANN] oVirt 3.5.0 Second Beta is now available
>>>> for	testing
>>>>
>>>> Il 23/07/2014 17:57, Alon Bar-Lev ha scritto:
>>>>>
>>>>> This is one week old software.
>>>>> People will not be able to check fixes that were introduced this week.
>>>>> Please issue snapshot before the test day.
>>>>
>>>> I'm not sure about what you're referring to. Most of the packages are from
>>>> this morning publisher job.
>>>> http://jenkins.ovirt.org/view/Publishers/job/publish_ovirt_rpms_nightly_3.5/28/console
>>>> packages not taken from there are taken from build provided by
>>>> maintainers.
>>>>
>>>> Can you detail what's so old in this release?
>>>> Thanks.
>>>>
>>>
>>> I look at the tag: ovirt-engine-3.5.0_beta2
>>> 8e1babcc5512e228336989dd34a601982af11834
>>>
>>> Date:   Mon Jul 21 09:18:39 2014 -0400
>>>
>>> Until Tue Jul 29th it will be more than two week old version.
>>>
>>> Isn't this the right tag?
>>>
>>> $ git log --oneline 8e1babcc5512e228336989dd34a601982af11834..HEAD | wc -l
>>> 21
>>>
>>
>> well, the publisher job took the latest available build which was:
>>
>> http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged/label=centos6-host/60/
>> completed yesterday morning at 02:21:12 AM taking sources from
>> 8e1babcc5512e228336989dd34a601982af11834.
>> All remaining patches were not included in that build. The build has been
>> done 16 hours before the official announce by jenkins.
>>
>> We needed to test it for basic sanity.
>> We just can't announce a beta including packages with patches just merged
>> without any kind of test on it.
>> If you want a bleeding edge build without any sanity test on it, you're
>> welcome to use daily 3.5 snapshot.
>> That's why we have it.
>>
> 
> it has nothing to do with bleeding edge... it is about asking subsystem maintainers if a tag is stable, instead of taking random.
> 
> for example: 6b9f795b0785fad1598cdddfed83cd9861bc4d71, fb7172bba8f729161694c584cec3a9e3d6989d97, 03dbc8bdb68600108a3befbfb819d422065a77ef infra would have probably nak beta at this hash.

This is a different issue than "This is one week old software" that started the thread.

I may agree on "asking subsystem maintainers if a tag is stable, instead of taking random".

That said, it's 2 weeks I'm asking maintainers to be sure that their packages build and works for the day before the build date and it's one week I'm
pinging people because engine didn't build at all.
I also sent an email to everyone having pending patches on 3.5 branch to be sure there weren't pending issues and I received just one reply on one
patch that is included in this beta release.
If this is not enough and if this is what maintainers want, I'll block next release until I have a written ack on every single package for each
subsystem involved.

This however is totally different than the decided procedure that the one currently in place for non GA releases and will imply that released rpms
will be older than one day for sure, since I'll need to take a starting point for getting acks, branching, asking all subsystem maintainers to be sure
to backport to the new branch whatever needs for gathering their ack. This means that the release process will need one lot more time to be completed.

Let me know what maintainers decide on this.

> 
>>>
>>>>
>>>>
>>>>
>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: "Sandro Bonazzola" <sbonazzo at redhat.com>
>>>>>> To: announce at ovirt.org, Users at ovirt.org, devel at ovirt.org
>>>>>> Sent: Wednesday, July 23, 2014 6:49:42 PM
>>>>>> Subject: [ovirt-users] [ANN] oVirt 3.5.0 Second Beta is now available
>>>>>> for
>>>>>> 	testing
>>>>>>
>>>>>> The oVirt team is pleased to announce that the 3.5.0 Second Beta is now
>>>>>> available for testing as of Jul 21th 2014.
>>>>>>
>>>>>> The beta is available now for Fedora 19, Fedora 20 and Red Hat
>>>>>> Enterprise
>>>>>> Linux 6.5
>>>>>> (or similar).
>>>>>>
>>>>>> Feel free to join us testing it on Tue Jul 29th second test day!
>>>>>>
>>>>>> This release of oVirt includes numerous bug fixes.
>>>>>> See the release notes [1] for a list of the new features and bugs fixed.
>>>>>>
>>>>>> The existing repository ovirt-3.5-pre has been updated for delivering
>>>>>> this
>>>>>> release without the need of enabling any other repository.
>>>>>>
>>>>>> Please refer to release notes [1] for Installation / Upgrade
>>>>>> instructions.
>>>>>> New oVirt Live, oVirt Guest Tools and oVirt Node ISO will be available
>>>>>> soon
>>>>>> as well[2].
>>>>>>
>>>>>> Please note that mirrors may need a couple of days before being
>>>>>> synchronized.
>>>>>> If you want to be sure to use latest rpms and don't want to wait for the
>>>>>> mirrors,
>>>>>> you can edit /etc/yum.repos.d/ovirt-3.5.repo commenting the mirror line
>>>>>> and
>>>>>> removing the comment on baseurl line.
>>>>>>
>>>>>> [1] http://www.ovirt.org/OVirt_3.5_Release_Notes
>>>>>> [2] http://resources.ovirt.org/pub/ovirt-3.5-pre/iso/
>>>>>>
>>>>>> --
>>>>>> Sandro Bonazzola
>>>>>> Better technology. Faster innovation. Powered by community
>>>>>> collaboration.
>>>>>> See how it works at redhat.com
>>>>>> _______________________________________________
>>>>>> Users mailing list
>>>>>> Users at ovirt.org
>>>>>> http://lists.ovirt.org/mailman/listinfo/users
>>>>>>
>>>>
>>>>
>>>> --
>>>> Sandro Bonazzola
>>>> Better technology. Faster innovation. Powered by community collaboration.
>>>> See how it works at redhat.com
>>>>
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>>

-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com