From mgoldboi at redhat.com Tue Jul 30 11:06:01 2013 Content-Type: multipart/mixed; boundary="===============4946160144898625040==" MIME-Version: 1.0 From: Moran Goldboim To: devel at ovirt.org Subject: [Engine-devel] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review] Date: Tue, 30 Jul 2013 18:05:46 +0300 Message-ID: <51F7D64A.4050103@redhat.com> --===============4946160144898625040== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable This is a multi-part message in MIME format. --------------080603010209010007090703 Content-Type: text/plain; charset=3DISO-8859-1; format=3Dflowed Content-Transfer-Encoding: 7bit We would like to go a head on oVirt 3.3 release process and issue an RC for tomorrow meeting: Maintainers/ Package owners =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D -branch your git repo (master) with 3.3 branch (making master ready for 3.4) -for tomorrow meeting, overview [1], see if you have any changes to it -if you don't have any blockers under your component, please branch 3.3 = with RC1 branch | -master | -engine_3.3 | -RC1 | -engine_3.2 ... Users =3D=3D=3D=3D with your experience from test day and with nightlies, if you feel there = are additional candidates to block this version for please add it to the = tracker bug [1]. Suggested Schedule =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Wed Jul 31st - review of blockers for the version and component readiness Mon Aug 5th - RC1 release Wed Aug 7th - Release readiness review (in case of blockers an RC2 will = be issued) Thanks. [1]*Bug 918494* = -Tracker: oVirt 3.3 release --------------080603010209010007090703 Content-Type: text/html; charset=3DISO-8859-1 Content-Transfer-Encoding: 7bit We would like to go a head on oVirt 3.3 release process and issue an RC

for tomorrow meeting:

Maintainers/ Package owners
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
-branch your git repo (master) with 3.3 branch (making master ready for 3.4)
-for tomorrow meeting, overview [1], see if you have any changes to it
-if you don't have any blockers under your component, please branch 3.3 with RC1 branch

    |   
    -master
    |   
    -engine_3.3
        |
        -RC1
    |
    -engine_3.2
    ...
  
Users
=3D=3D=3D=3D
with your experience from test day and with nightlies, if you feel there are additional candidates to block this version for please add it to the tracker bug [1].

Suggested Schedule
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Wed Jul 31st - review of blockers for the version and component readiness
Mon Aug 5th - RC1 release
Wed Aug 7th - Release readiness review (in case of blockers an RC2 will be issued)

Thanks.

[1]Bug&= nbsp;918494 - Tracker: oVirt 3.3 release


 --------------080603010209010007090703-- --===============4946160144898625040== Content-Type: multipart/alternative MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="attachment.bin" VGhpcyBpcyBhIG11bHRpLXBhcnQgbWVzc2FnZSBpbiBNSU1FIGZvcm1hdC4KLS0tLS0tLS0tLS0t LS0wODA2MDMwMTAyMDkwMTAwMDcwOTA3MDMKQ29udGVudC1UeXBlOiB0ZXh0L3BsYWluOyBjaGFy c2V0PUlTTy04ODU5LTE7IGZvcm1hdD1mbG93ZWQKQ29udGVudC1UcmFuc2Zlci1FbmNvZGluZzog N2JpdAoKV2Ugd291bGQgbGlrZSB0byBnbyBhIGhlYWQgb24gb1ZpcnQgMy4zIHJlbGVhc2UgcHJv Y2VzcyBhbmQgaXNzdWUgYW4gUkMKCmZvciB0b21vcnJvdyBtZWV0aW5nOgoKTWFpbnRhaW5lcnMv IFBhY2thZ2Ugb3duZXJzCj09PT09PT09PT09PT09PT09PQotYnJhbmNoIHlvdXIgZ2l0IHJlcG8g KG1hc3Rlcikgd2l0aCAzLjMgYnJhbmNoIChtYWtpbmcgbWFzdGVyIHJlYWR5IGZvciAzLjQpCi1m b3IgdG9tb3Jyb3cgbWVldGluZywgb3ZlcnZpZXcgWzFdLCBzZWUgaWYgeW91IGhhdmUgYW55IGNo YW5nZXMgdG8gaXQKLWlmIHlvdSBkb24ndCBoYXZlIGFueSBibG9ja2VycyB1bmRlciB5b3VyIGNv bXBvbmVudCwgcGxlYXNlIGJyYW5jaCAzLjMgCndpdGggUkMxIGJyYW5jaAoKICAgICB8CiAgICAg LW1hc3RlcgogICAgIHwKICAgICAtZW5naW5lXzMuMwogICAgICAgICB8CiAgICAgICAgIC1SQzEK ICAgICB8CiAgICAgLWVuZ2luZV8zLjIKICAgICAuLi4KClVzZXJzCj09PT0Kd2l0aCB5b3VyIGV4 cGVyaWVuY2UgZnJvbSB0ZXN0IGRheSBhbmQgd2l0aCBuaWdodGxpZXMsIGlmIHlvdSBmZWVsIHRo ZXJlIAphcmUgYWRkaXRpb25hbCBjYW5kaWRhdGVzIHRvIGJsb2NrIHRoaXMgdmVyc2lvbiBmb3Ig cGxlYXNlIGFkZCBpdCB0byB0aGUgCnRyYWNrZXIgYnVnIFsxXS4KClN1Z2dlc3RlZCBTY2hlZHVs ZQo9PT09PT09PT09PT0KV2VkIEp1bCAzMXN0IC0gcmV2aWV3IG9mIGJsb2NrZXJzIGZvciB0aGUg dmVyc2lvbiBhbmQgY29tcG9uZW50IHJlYWRpbmVzcwpNb24gQXVnIDV0aCAtIFJDMSByZWxlYXNl CldlZCBBdWcgN3RoIC0gUmVsZWFzZSByZWFkaW5lc3MgcmV2aWV3IChpbiBjYXNlIG9mIGJsb2Nr ZXJzIGFuIFJDMiB3aWxsIApiZSBpc3N1ZWQpCgpUaGFua3MuCgpbMV0qQnVnIDkxODQ5NCogPGh0 dHBzOi8vYnVnemlsbGEucmVkaGF0LmNvbS9zaG93X2J1Zy5jZ2k/aWQ9OTE4NDk0PiAKLVRyYWNr ZXI6IG9WaXJ0IDMuMyByZWxlYXNlCgoKCi0tLS0tLS0tLS0tLS0tMDgwNjAzMDEwMjA5MDEwMDA3 MDkwNzAzCkNvbnRlbnQtVHlwZTogdGV4dC9odG1sOyBjaGFyc2V0PUlTTy04ODU5LTEKQ29udGVu dC1UcmFuc2Zlci1FbmNvZGluZzogN2JpdAoKPGh0bWw+CiAgPGhlYWQ+CgogICAgPG1ldGEgaHR0 cC1lcXVpdj0iY29udGVudC10eXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9SVNPLTg4 NTktMSI+CiAgPC9oZWFkPgogIDxib2R5IGJnY29sb3I9IiNGRkZGRkYiIHRleHQ9IiMwMDAwMDAi PgogICAgV2Ugd291bGQgbGlrZSB0byBnbyBhIGhlYWQgb24gb1ZpcnQgMy4zIHJlbGVhc2UgcHJv Y2VzcyBhbmQgaXNzdWUgYW4KICAgIFJDIDxicj4KICAgIDxicj4KICAgIGZvciB0b21vcnJvdyBt ZWV0aW5nOjxicj4KICAgIDxicj4KICAgIE1haW50YWluZXJzLyBQYWNrYWdlIG93bmVycyA8YnI+ CiAgICA9PT09PT09PT09PT09PT09PT08YnI+CiAgICAtYnJhbmNoIHlvdXIgZ2l0IHJlcG8gKG1h c3Rlcikgd2l0aCAzLjMgYnJhbmNoIChtYWtpbmcgbWFzdGVyIHJlYWR5CiAgICBmb3IgMy40KTxi cj4KICAgIC1mb3IgdG9tb3Jyb3cgbWVldGluZywgb3ZlcnZpZXcgWzFdPHNwYW4KICAgICAgaWQ9 InN1bW1hcnlfYWxpYXNfY29udGFpbmVyIj48c3BhbiBpZD0ic2hvcnRfZGVzY19ub25lZGl0X2Rp c3BsYXkiPiwKICAgICAgICBzZWUgaWYgeW91IGhhdmUgYW55IGNoYW5nZXMgdG8gaXQ8YnI+CiAg ICAgICAgLWlmIHlvdSBkb24ndCBoYXZlIGFueSBibG9ja2VycyB1bmRlciB5b3VyIGNvbXBvbmVu dCwgcGxlYXNlCiAgICAgICAgYnJhbmNoIDMuMyB3aXRoIFJDMSBicmFuY2g8YnI+CiAgICAgICAg PGJyPgogICAgICAgICZuYnNwOyZuYnNwOyZuYnNwOyB8Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxicj4K ICAgICAgICAmbmJzcDsmbmJzcDsmbmJzcDsgLW1hc3Rlcjxicj4KICAgICAgICAmbmJzcDsmbmJz cDsmbmJzcDsgfCZuYnNwOyZuYnNwOyZuYnNwOyA8YnI+CiAgICAgICAgJm5ic3A7Jm5ic3A7Jm5i c3A7IC1lbmdpbmVfMy4zPGJyPgogICAgICAgICZuYnNwOyZuYnNwOyAmbmJzcDsmbmJzcDsgJm5i c3A7IHw8YnI+CiAgICAgICAgJm5ic3A7Jm5ic3A7Jm5ic3A7ICZuYnNwOyZuYnNwOyZuYnNwOyAt UkMxPGJyPgogICAgICAgICZuYnNwOyZuYnNwOyZuYnNwOyB8PGJyPgogICAgICAgICZuYnNwOyZu YnNwOyZuYnNwOyAtZW5naW5lXzMuMjxicj4KICAgICAgICAmbmJzcDsmbmJzcDsmbmJzcDsgLi4u PGJyPgogICAgICAgICZuYnNwOyZuYnNwOyA8YnI+CiAgICAgICAgVXNlcnM8YnI+CiAgICAgICAg PT09PTxicj4KICAgICAgICB3aXRoIHlvdXIgZXhwZXJpZW5jZSBmcm9tIHRlc3QgZGF5IGFuZCB3 aXRoIG5pZ2h0bGllcywgaWYgeW91CiAgICAgICAgZmVlbCB0aGVyZSBhcmUgYWRkaXRpb25hbCBj YW5kaWRhdGVzIHRvIGJsb2NrIHRoaXMgdmVyc2lvbiBmb3IKICAgICAgICBwbGVhc2UgYWRkIGl0 IHRvIHRoZSB0cmFja2VyIGJ1ZyBbMV0uPGJyPgogICAgICAgIDxicj4KICAgICAgICBTdWdnZXN0 ZWQgU2NoZWR1bGU8YnI+CiAgICAgICAgPT09PT09PT09PT09PGJyPgogICAgICAgIFdlZCBKdWwg MzFzdCAtIHJldmlldyBvZiBibG9ja2VycyBmb3IgdGhlIHZlcnNpb24gYW5kIGNvbXBvbmVudAog ICAgICAgIHJlYWRpbmVzczxicj4KICAgICAgICBNb24gQXVnIDV0aCAtIFJDMSByZWxlYXNlPGJy PgogICAgICAgIFdlZCBBdWcgN3RoIC0gUmVsZWFzZSByZWFkaW5lc3MgcmV2aWV3IChpbiBjYXNl IG9mIGJsb2NrZXJzIGFuCiAgICAgICAgUkMyIHdpbGwgYmUgaXNzdWVkKTxicj4KICAgICAgPC9z cGFuPjwvc3Bhbj48c3BhbiBpZD0ic3VtbWFyeV9hbGlhc19jb250YWluZXIiPjxzcGFuCiAgICAg ICAgaWQ9InNob3J0X2Rlc2Nfbm9uZWRpdF9kaXNwbGF5Ij48c3BhbgogICAgICAgICAgaWQ9InN1 bW1hcnlfYWxpYXNfY29udGFpbmVyIj48c3BhbgogICAgICAgICAgICBpZD0ic2hvcnRfZGVzY19u b25lZGl0X2Rpc3BsYXkiPjxicj4KICAgICAgICAgICAgVGhhbmtzLjwvc3Bhbj48L3NwYW4+IDxi cj4KICAgICAgICA8YnI+CiAgICAgICAgWzFdPC9zcGFuPjwvc3Bhbj48YQogICAgICBocmVmPSJo dHRwczovL2J1Z3ppbGxhLnJlZGhhdC5jb20vc2hvd19idWcuY2dpP2lkPTkxODQ5NCI+PGI+QnVn Jm5ic3A7OTE4NDk0PC9iPjwvYT4KICAgIC08c3BhbiBpZD0ic3VtbWFyeV9hbGlhc19jb250YWlu ZXIiPiA8c3BhbgogICAgICAgIGlkPSJzaG9ydF9kZXNjX25vbmVkaXRfZGlzcGxheSI+VHJhY2tl cjogb1ZpcnQgMy4zIHJlbGVhc2U8YnI+CiAgICAgICAgPGJyPgogICAgICAgIDxicj4KICAgICAg PC9zcGFuPjwvc3Bhbj4KICA8L2JvZHk+CjwvaHRtbD4KCi0tLS0tLS0tLS0tLS0tMDgwNjAzMDEw MjA5MDEwMDA3MDkwNzAzLS0K --===============4946160144898625040==-- From alonbl at redhat.com Tue Jul 30 11:10:28 2013 Content-Type: multipart/mixed; boundary="===============7050231802011478888==" MIME-Version: 1.0 From: Alon Bar-Lev To: devel at ovirt.org Subject: Re: [Engine-devel] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review] Date: Tue, 30 Jul 2013 11:10:26 -0400 Message-ID: <834354904.4127994.1375197026698.JavaMail.root@redhat.com> In-Reply-To: 51F7D64A.4050103@redhat.com --===============7050231802011478888== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable ----- Original Message ----- > From: "Moran Goldboim" > To: "engine-devel" , vdsm-devel(a)ovirt.org, us= ers(a)ovirt.org > Sent: Tuesday, July 30, 2013 6:05:46 PM > Subject: [Engine-devel] [ATN] oVirt 3.3 release, moving to RC [3.3 branch= ing, blockers review] > = > We would like to go a head on oVirt 3.3 release process and issue an RC > = > for tomorrow meeting: > = > Maintainers/ Package owners > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > -branch your git repo (master) with 3.3 branch (making master ready for 3= .4) > -for tomorrow meeting, overview [1] , see if you have any changes to it > -if you don't have any blockers under your component, please branch 3.3 w= ith > RC1 branch > = > | = > -master > | = > -engine_3.3 > | = > -RC1 > | = > -engine_3.2 Please use proper notation... ovirt-engine-3.3.0 branch for 3.3.0 release cycle ovirt-engine-3.3.0_rc1 - for rc1 tag or branch > ... > = > Users > =3D=3D=3D=3D > with your experience from test day and with nightlies, if you feel there = are > additional candidates to block this version for please add it to the trac= ker > bug [1]. > = > Suggested Schedule > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Wed Jul 31st - review of blockers for the version and component readiness > Mon Aug 5th - RC1 release > Wed Aug 7th - Release readiness review (in case of blockers an RC2 will be > issued) > = > Thanks. > = > [1] Bug 918494 - Tracker: oVirt 3.3 release > = > = > = > _______________________________________________ > Engine-devel mailing list > Engine-devel(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/engine-devel >=20 --===============7050231802011478888==-- From danken at redhat.com Tue Jul 30 12:58:31 2013 Content-Type: multipart/mixed; boundary="===============0788371715684092997==" MIME-Version: 1.0 From: Dan Kenigsberg To: devel at ovirt.org Subject: Re: [Engine-devel] [Users] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review] Date: Tue, 30 Jul 2013 19:58:27 +0300 Message-ID: <20130730165827.GA22332@redhat.com> In-Reply-To: 51F7D64A.4050103@redhat.com --===============0788371715684092997== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Jul 30, 2013 at 06:05:46PM +0300, Moran Goldboim wrote: > We would like to go a head on oVirt 3.3 release process and issue an RC > = > for tomorrow meeting: > = > Maintainers/ Package owners > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > -branch your git repo (master) with 3.3 branch (making master ready for 3= .4) > -for tomorrow meeting, overview [1], see if you have any changes to it > -if you don't have any blockers under your component, please branch > 3.3 with RC1 branch > = > | > -master > | > -engine_3.3 > | > -RC1 > | > -engine_3.2 > ... > = > Users > =3D=3D=3D=3D > with your experience from test day and with nightlies, if you feel > there are additional candidates to block this version for please add > it to the tracker bug [1]. > = > Suggested Schedule > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Wed Jul 31st - review of blockers for the version and component readiness > Mon Aug 5th - RC1 release > Wed Aug 7th - Release readiness review (in case of blockers an RC2 > will be issued) > = > Thanks. > = > [1]*Bug 918494* > -Tracker: oVirt 3.3 release I've just tagged vdsm-4.12.0 and branched ovirt-3.3 branch for the vdsm repository starting at git has 620343d6317c849fc985a5083cebb68c995f7c15. Expect a deluge of non-ovirt-3.3 merges to the master branch soon. Future ovirt-3.3 fixes would have to be backported and cherry-picked. Dan. --===============0788371715684092997==-- From iheim at redhat.com Tue Jul 30 14:56:43 2013 Content-Type: multipart/mixed; boundary="===============1216556096326033983==" MIME-Version: 1.0 From: Itamar Heim To: devel at ovirt.org Subject: Re: [Engine-devel] [Users] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review] Date: Tue, 30 Jul 2013 21:56:40 +0300 Message-ID: <51F80C68.3000709@redhat.com> In-Reply-To: 51F7D64A.4050103@redhat.com --===============1216556096326033983== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 07/30/2013 06:05 PM, Moran Goldboim wrote: > We would like to go a head on oVirt 3.3 release process and issue an RC how can we do this before folks review all the bugs with target release = of 3.3 and either suggest them as blockers or move them from 3.3? there are currently 59 NEW, 7 ASSIGNED and 22 POST with target release = of 3.3? http://alturl.com/aq23x > > for tomorrow meeting: > > Maintainers/ Package owners > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > -branch your git repo (master) with 3.3 branch (making master ready for 3= .4) > -for tomorrow meeting, overview [1], see if you have any changes to it > -if you don't have any blockers under your component, please branch 3.3 > with RC1 branch > > | > -master > | > -engine_3.3 > | > -RC1 > | > -engine_3.2 > ... > > Users > =3D=3D=3D=3D > with your experience from test day and with nightlies, if you feel there > are additional candidates to block this version for please add it to the > tracker bug [1]. > > Suggested Schedule > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Wed Jul 31st - review of blockers for the version and component readiness > Mon Aug 5th - RC1 release > Wed Aug 7th - Release readiness review (in case of blockers an RC2 will > be issued) > > Thanks. > > [1]*Bug 918494* > -Tracker: oVirt 3.3 release > > > > > _______________________________________________ > Users mailing list > Users(a)ovirt.org > http://lists.ovirt.org/mailman/listinfo/users > --===============1216556096326033983==-- From mgoldboi at redhat.com Tue Jul 30 15:01:55 2013 Content-Type: multipart/mixed; boundary="===============0362562555470060208==" MIME-Version: 1.0 From: Moran Goldboim To: devel at ovirt.org Subject: Re: [Engine-devel] [Users] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review] Date: Tue, 30 Jul 2013 22:01:44 +0300 Message-ID: <51F80D98.2070703@redhat.com> In-Reply-To: 51F80C68.3000709@redhat.com --===============0362562555470060208== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On 07/30/2013 09:56 PM, Itamar Heim wrote: > On 07/30/2013 06:05 PM, Moran Goldboim wrote: >> We would like to go a head on oVirt 3.3 release process and issue an RC > > how can we do this before folks review all the bugs with target = > release of 3.3 and either suggest them as blockers or move them from 3.3? > there are currently 59 NEW, 7 ASSIGNED and 22 POST with target release = > of 3.3? > > http://alturl.com/aq23x that the aim of this mail, maintainers should review their realm for = blockers (unscrubbed bugs as well), and this release should get into = stabilization mode. by tomorrow we should have a better view on what are the blockers for = the version, we are already going to delay this release, and i would = like to get a clear view by tomorrow, as mentioned later in the mail - = RC should go out without any known blockers. > >> >> for tomorrow meeting: >> >> Maintainers/ Package owners >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> -branch your git repo (master) with 3.3 branch (making master ready = >> for 3.4) >> -for tomorrow meeting, overview [1], see if you have any changes to it >> -if you don't have any blockers under your component, please branch 3.3 >> with RC1 branch >> >> | >> -master >> | >> -engine_3.3 >> | >> -RC1 >> | >> -engine_3.2 >> ... >> >> Users >> =3D=3D=3D=3D >> with your experience from test day and with nightlies, if you feel there >> are additional candidates to block this version for please add it to the >> tracker bug [1]. >> >> Suggested Schedule >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D >> Wed Jul 31st - review of blockers for the version and component = >> readiness >> Mon Aug 5th - RC1 release >> Wed Aug 7th - Release readiness review (in case of blockers an RC2 will >> be issued) >> >> Thanks. >> >> [1]*Bug 918494* >> -Tracker: oVirt 3.3 release >> >> >> >> >> _______________________________________________ >> Users mailing list >> Users(a)ovirt.org >> http://lists.ovirt.org/mailman/listinfo/users >> > --===============0362562555470060208==-- From danken at redhat.com Tue Jul 30 17:49:11 2013 Content-Type: multipart/mixed; boundary="===============7287641892059428878==" MIME-Version: 1.0 From: Dan Kenigsberg To: devel at ovirt.org Subject: Re: [Engine-devel] [Users] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review] Date: Wed, 31 Jul 2013 00:49:07 +0300 Message-ID: <20130730214907.GD24058@redhat.com> In-Reply-To: 51F7D64A.4050103@redhat.com --===============7287641892059428878== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, Jul 30, 2013 at 06:05:46PM +0300, Moran Goldboim wrote: > We would like to go a head on oVirt 3.3 release process and issue an RC > = > for tomorrow meeting: > = > Maintainers/ Package owners > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > -branch your git repo (master) with 3.3 branch (making master ready for 3= .4) > -for tomorrow meeting, overview [1], see if you have any changes to it > -if you don't have any blockers under your component, please branch > 3.3 with RC1 branch > = > | > -master > | > -engine_3.3 > | > -RC1 > | > -engine_3.2 > ... > = > Users > =3D=3D=3D=3D > with your experience from test day and with nightlies, if you feel > there are additional candidates to block this version for please add > it to the tracker bug [1]. > = > Suggested Schedule > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > Wed Jul 31st - review of blockers for the version and component readiness > Mon Aug 5th - RC1 release > Wed Aug 7th - Release readiness review (in case of blockers an RC2 > will be issued) > = > Thanks. > = > [1]*Bug 918494* > -Tracker: oVirt 3.3 release I've just tagged vdsm-4.12.0 and branched ovirt-3.3 branch for the vdsm repository starting at git has 620343d6317c849fc985a5083cebb68c995f7c15. Expect a deluge of non-ovirt-3.3 merges to the master branch soon. Future ovirt-3.3 fixes would have to be backported and cherry-picked. Dan. --===============7287641892059428878==--