[Users] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, blockers review]
This is a multi-part message in MIME format. --------------080603010209010007090703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 ================== -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 ==== 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 ============ 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* <https://bugzilla.redhat.com/show_bug.cgi?id=918494> -Tracker: oVirt 3.3 release --------------080603010209010007090703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit <html> <head> <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1"> </head> <body bgcolor="#FFFFFF" text="#000000"> We would like to go a head on oVirt 3.3 release process and issue an RC <br> <br> for tomorrow meeting:<br> <br> Maintainers/ Package owners <br> ==================<br> -branch your git repo (master) with 3.3 branch (making master ready for 3.4)<br> -for tomorrow meeting, overview [1]<span id="summary_alias_container"><span id="short_desc_nonedit_display">, see if you have any changes to it<br> -if you don't have any blockers under your component, please branch 3.3 with RC1 branch<br> <br> | <br> -master<br> | <br> -engine_3.3<br> |<br> -RC1<br> |<br> -engine_3.2<br> ...<br> <br> Users<br> ====<br> 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].<br> <br> Suggested Schedule<br> ============<br> Wed Jul 31st - review of blockers for the version and component readiness<br> Mon Aug 5th - RC1 release<br> Wed Aug 7th - Release readiness review (in case of blockers an RC2 will be issued)<br> </span></span><span id="summary_alias_container"><span id="short_desc_nonedit_display"><span id="summary_alias_container"><span id="short_desc_nonedit_display"><br> Thanks.</span></span> <br> <br> [1]</span></span><a href="https://bugzilla.redhat.com/show_bug.cgi?id=918494"><b>Bug 918494</b></a> -<span id="summary_alias_container"> <span id="short_desc_nonedit_display">Tracker: oVirt 3.3 release<br> <br> <br> </span></span> </body> </html> --------------080603010209010007090703--
----- Original Message -----
From: "Moran Goldboim" <mgoldboi@redhat.com> To: "engine-devel" <engine-devel@ovirt.org>, vdsm-devel@ovirt.org, users@ovirt.org Sent: Tuesday, July 30, 2013 6:05:46 PM Subject: [Engine-devel] [ATN] oVirt 3.3 release, moving to RC [3.3 branching, 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 ================== -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
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 ==== 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 ============ 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@ovirt.org http://lists.ovirt.org/mailman/listinfo/engine-devel
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 ================== -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 ==== 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 ============ 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* <https://bugzilla.redhat.com/show_bug.cgi?id=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.
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 ================== -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 ==== 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 ============ 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* <https://bugzilla.redhat.com/show_bug.cgi?id=918494> -Tracker: oVirt 3.3 release
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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?
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 ================== -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 ==== 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 ============ 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* <https://bugzilla.redhat.com/show_bug.cgi?id=918494> -Tracker: oVirt 3.3 release
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
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 ================== -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 ==== 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 ============ 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* <https://bugzilla.redhat.com/show_bug.cgi?id=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.
participants (4)
-
Alon Bar-Lev -
Dan Kenigsberg -
Itamar Heim -
Moran Goldboim