<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi,<br>
<br>
I just reviewed the Release Notes, and came across this cryptic
passage at
<a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_3.5_Release_Notes#What_does_this_change_mean_for_the_admin.3F">http://www.ovirt.org/OVirt_3.5_Release_Notes#What_does_this_change_mean_for_the_admin.3F</a>
:<br>
<br>
<blockquote type="cite">Thus, it is of utmost importance that <b>if
you have ifcfg handmade customizations that you port those
changes to be use custom network properties and write a hook to
apply them</b>.
</blockquote>
<br>
I have no idea what this means, and suspect I'm not alone among the
readers. Some examples and/or links would be very helpful here.<br>
<br>
Thanks,<br>
Bob<br>
<br>
<div class="moz-cite-prefix">On 09/17/2014 07:46 AM, Sandro
Bonazzola wrote:<br>
</div>
<blockquote cite="mid:54197482.8070301@redhat.com" type="cite">
<pre wrap="">Hi,
We are going to start composing oVirt 3.5.0 GA (or RC3, depending on Test Day results and oVirt Sync Meeting decisions) on Monday 2014-09-22.
Maintainers:
- Please be sure that 3.5 snapshot satisfy release criteria[9]
- Please be sure that no pending patches are going to block the release
- If any patch must block the GA release please raise the issue as soon as possible.
- If any packages need a rebase please raise the issue as soon as possible.
- Be aware that packages that doesn't need a rebase must be re-built with final release versioning from the RC2 tag.
The bug tracker [1] shows the following proposed blockers to be reviewed:
Bug ID        Whiteboard        Status        Summary
1142256        integration        POST        engine-setup does not write conf file to allow accessing reports
And the following dependencies still open:
Bug 1041569 - [NFR] libvirt: Returning the watermark for all the images opened for writing
Bug 1102881 - virDomainBlockCommit fails with live snapshots on oVirt block storage
The following bugs are keyworded as Regression and not marked as blockers[10]
Bug ID        Whiteboard        Status        Summary
1135909        infra                POST        [Event log] Wrong warning about available swap memory of host [1023MB], when actually host has [1024MB] memory size
1118349        storage                NEW        [vdsm] Creating DataCenter 3.5 using master domain V1 fails with InquireNotSupportedError
1110444        ux                POST        bookmark selection does not work on first try
1138314        virt                NEW        Fail to start vm with payload.
Feature freeze is now effective, and branch has been created.
All new patches must be backported to 3.5 branch too.
Features completed are marked in green on Features Status Table [2]
There are still 83 bugs [3] targeted to 3.5.0.
Excluding node and documentation bugs we still have 58 bugs [4] targeted to 3.5.0.
More in detail [5]:
Whiteboard        NEW        ASSIGNED        POST        Total
docs                14        1                0        15
gluster                9        4                2        15
i18n                0        0                1        1
integration        1        1                1        3
node                6        4                0        10
ppc                2        0                4        6
sla                5        0                8        13
storage                0        0                3        3
virt                12        0                5        17
Total                49        10                24        83
Maintainers / Assignee:
- Please ensure that completed features are marked in green on Features Status Table [2]
- If you find a blocker bug please remember to add it to the tracker [1]
- Please fill release notes, the page has been created here [6]
- Please review results from Third Test Day [7]
- Please update the target to 3.5.1 or later for bugs that won't be in 3.5.0:
it will ease gathering the blocking bugs for next releases.
Community:
- You're welcome to join us testing next release candidate and getting involved in oVirt Quality Assurance[8]
[1] <a class="moz-txt-link-freetext" href="http://bugzilla.redhat.com/1073943">http://bugzilla.redhat.com/1073943</a>
[2] <a class="moz-txt-link-freetext" href="http://goo.gl/4SuYdE">http://goo.gl/4SuYdE</a>
[3] <a class="moz-txt-link-freetext" href="http://red.ht/1pVEk7H">http://red.ht/1pVEk7H</a>
[4] <a class="moz-txt-link-freetext" href="http://red.ht/1zT2mSq">http://red.ht/1zT2mSq</a>
[5] <a class="moz-txt-link-freetext" href="http://red.ht/1q7SqNL">http://red.ht/1q7SqNL</a>
[6] <a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_3.5_Release_Notes">http://www.ovirt.org/OVirt_3.5_Release_Notes</a>
[7] <a class="moz-txt-link-freetext" href="http://etherpad.ovirt.org/p/3.5-testday-3">http://etherpad.ovirt.org/p/3.5-testday-3</a>
[8] <a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_Quality_Assurance">http://www.ovirt.org/OVirt_Quality_Assurance</a>
[9] <a class="moz-txt-link-freetext" href="http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29">http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria_.28WIP.29</a>
[10] <a class="moz-txt-link-freetext" href="http://goo.gl/uavikG">http://goo.gl/uavikG</a>
Thanks,
</pre>
</blockquote>
<br>
</body>
</html>