Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
Dan.
On 10/09/2013 07:55 AM, Dan Kenigsberg wrote:
Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
+1
----- Original Message -----
On 10/09/2013 07:55 AM, Dan Kenigsberg wrote:
Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
+1
+1
-- Cheers Douglas _______________________________________________ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
----- Original Message -----
From: "Dan Kenigsberg" danken@redhat.com To: vdsm-devel@fedorahosted.org, arch@ovirt.org Sent: Wednesday, October 9, 2013 1:55:03 PM Subject: suggesting Yaniv Bronheim as ovirt-3.3 branch maintainer
Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
+1
Yaniv has a keen eye for catching system breaking failures and I think he'll be an invaluable addition to the stable branch management.
+1
----- Original Message -----
From: "Dan Kenigsberg" danken@redhat.com To: vdsm-devel@fedorahosted.org, arch@ovirt.org Sent: Wednesday, October 9, 2013 2:55:03 PM Subject: suggesting Yaniv Bronheim as ovirt-3.3 branch maintainer
Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
Dan. _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
+1
On 10/09/2013 02:55 PM, Dan Kenigsberg wrote:
Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
Dan. _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
On 10/13/2013 04:41 PM, Maor Lipchuk wrote:
+1
On 10/09/2013 02:55 PM, Dan Kenigsberg wrote:
Recently, the Vdsm branch ovirt-3.3 was rebased on a relatively-stabilized vdsm-4.13.0.
As discussed elsewhere, oVirt-3.3.1 is expected to be a relatively large micro version. Plenty of bug fixes are expected to be suggested to this branch.
Currently, Federico is responsible to merge patches for oVirt-3.3.1, with my assistance. I would like to nominate Yaniv to join us in this delicate task: on one hand we should fix as many problems, but on the other hand - avoid regressions and needless surprises. It is a micro version after all.
Yaniv has a wide understanding of Vdsm internals, and I am certain he would know how to solve problems introduced by patches approved by him.
Please grant him +2 and merge rights on the ovirt-3.3 branch of vdsm.
Dan. _______________________________________________ Arch mailing list Arch@ovirt.org http://lists.ovirt.org/mailman/listinfo/arch
vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
yaniv was added as vdsm stable branch maintainer (together with danken and federico)
vdsm-devel@lists.fedorahosted.org