Hello All. Since oVirt 4.3.0 released are we ready to branch master into 4.3? Thanks. -- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided. Thanks, Milan
Hello Milan. We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly. Any thoughts for engine? Should it also target Feb 18? Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.
Martin Perina <mperina@redhat.com> writes:
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?
Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
Hello Milan. Yes. You can do that. Thanks.
On 7 Feb 2019, at 22:06, Milan Zamazal <mzamazal@redhat.com> wrote:
Martin Perina <mperina@redhat.com> writes:
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?
Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
On Thu, Feb 7, 2019 at 10:06 PM Milan Zamazal <mzamazal@redhat.com> wrote:
Martin Perina <mperina@redhat.com> writes:
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?
I think we need to branch VDSM first and right after branching merge tge patch introducing 4.4 support https://gerrit.ovirt.org/96632 When VDSM with the patch merged will pass OST, we can branch engine and merge https://gerrit.ovirt.org/96631 If we will do that in different order, then master OST will be broken But what I wanted to mention is that we should branch either early enough to be able to deliver 4.3.1 without any issues or right after 4.3.1 is out to have everything ready before 4.3.2 work starts.
Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.
On Fri, Feb 8, 2019 at 9:34 AM Martin Perina <mperina@redhat.com> wrote:
On Thu, Feb 7, 2019 at 10:06 PM Milan Zamazal <mzamazal@redhat.com> wrote:
Martin Perina <mperina@redhat.com> writes:
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?
I think we need to branch VDSM first and right after branching merge tge patch introducing 4.4 support https://gerrit.ovirt.org/96632
We want vdsm-4.30.z to support engine-4.4. Thus I don't see why we should wait for anything. https://gerrit.ovirt.org/96632 should be in yesterday.
When VDSM with the patch merged will pass OST, we can branch engine and merge https://gerrit.ovirt.org/96631 If we will do that in different order, then master OST will be broken
But what I wanted to mention is that we should branch either early enough to be able to deliver 4.3.1 without any issues or right after 4.3.1 is out to have everything ready before 4.3.2 work starts.
Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o. _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HVBZ4UAZGGSARW...
On Fri, Feb 8, 2019 at 9:42 AM Dan Kenigsberg <danken@redhat.com> wrote:
On Fri, Feb 8, 2019 at 9:34 AM Martin Perina <mperina@redhat.com> wrote:
On Thu, Feb 7, 2019 at 10:06 PM Milan Zamazal <mzamazal@redhat.com> wrote:
Martin Perina <mperina@redhat.com> writes:
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date in mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?
I think we need to branch VDSM first and right after branching merge tge patch introducing 4.4 support https://gerrit.ovirt.org/96632
We want vdsm-4.30.z to support engine-4.4. Thus I don't see why we should wait for anything. https://gerrit.ovirt.org/96632 should be in yesterday.
argh, I should read closer before I hit Send. That patch in its current form should wait after branchout of vdsm, as it introduces clusterLevel 4.4, not only Engine 4.4. Why do you find it urgent to introduce clusterLevel 4.4? Are there pending Engine feature waiting on it?
When VDSM with the patch merged will pass OST, we can branch engine and merge https://gerrit.ovirt.org/96631 If we will do that in different order, then master OST will be broken
But what I wanted to mention is that we should branch either early enough to be able to deliver 4.3.1 without any issues or right after 4.3.1 is out to have everything ready before 4.3.2 work starts.
Anton.
On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com> wrote:
Anton Marchukov <amarchuk@redhat.com> writes:
> Since oVirt 4.3.0 released are we ready to branch master into 4.3?
Regarding Vdsm, there is still an ongoing storage work for 4.3 and no really strong pressure for branching out 4.3 I'm aware of. For that reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 branch on February 18 (and no significantly later than that). If the branch is needed earlier for infra or other reasons, we can make it. Storage work would have to be backported, but that can be mostly trivial if an initial master-merge rush is avoided.
Thanks, Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o. _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HVBZ4UAZGGSARW...
On Fri, Feb 8, 2019 at 8:45 AM Dan Kenigsberg <danken@redhat.com> wrote:
On Fri, Feb 8, 2019 at 9:42 AM Dan Kenigsberg <danken@redhat.com> wrote:
On Fri, Feb 8, 2019 at 9:34 AM Martin Perina <mperina@redhat.com> wrote:
On Thu, Feb 7, 2019 at 10:06 PM Milan Zamazal <mzamazal@redhat.com>
wrote:
Martin Perina <mperina@redhat.com> writes:
On Tue, Feb 5, 2019 at 10:37 AM Anton Marchukov <
amarchuk@redhat.com> wrote:
Hello Milan.
We do not necessary need it earlier, but we want to have some date
in
mind, so we can plan our CI work accordingly.
Any thoughts for engine? Should it also target Feb 18?
On Feb 19th we should release oVirt 4.3.1 RC (4.3.1 GA na Feb 26th along with RHV 4.3 beta 2), so I'd say let's branch after the final 4.3.1 build ...
I believe we needn't branch out Vdsm and Engine on the same date, right? So we can branch out Vdsm earlier than Engine, around Feb 18-19, is it OK?
I think we need to branch VDSM first and right after branching merge tge patch introducing 4.4 support https://gerrit.ovirt.org/96632
We want vdsm-4.30.z to support engine-4.4. Thus I don't see why we should wait for anything. https://gerrit.ovirt.org/96632 should be in yesterday.
argh, I should read closer before I hit Send. That patch in its current form should wait after branchout of vdsm, as it introduces clusterLevel 4.4, not only Engine 4.4. Why do you find it urgent to introduce clusterLevel 4.4? Are there pending Engine feature waiting on it?
No features yet, but we need to introduce 4.4 version and bump database versions, otherwise we will have issues for upgrades between 4.3 and 4.4 (database upgrade scripts in starting wiht 04_03_NNNN_*.sql needs to have the same NNNN in both 4.3 and master branches, otherwise they won't be applied properly on upgrade). This is nothing new, it always worked like this and introduced new version in master right after stable version is branched.
When VDSM with the patch merged will pass OST, we can branch engine
If we will do that in different order, then master OST will be broken
But what I wanted to mention is that we should branch either early enough to be able to deliver 4.3.1 without any issues or right after 4.3.1 is out to have everything ready before 4.3.2 work starts.
Anton.
> On 4 Feb 2019, at 15:41, Milan Zamazal <mzamazal@redhat.com>
wrote:
> > Anton Marchukov <amarchuk@redhat.com> writes: > >> Since oVirt 4.3.0 released are we ready to branch master into 4.3? > > Regarding Vdsm, there is still an ongoing storage work for 4.3 and no > really strong pressure for branching out 4.3 I'm aware of. For
> reason, Vdsm developers have agreed that we could create Vdsm ovirt-4.3 > branch on February 18 (and no significantly later than that). If the > branch is needed earlier for infra or other reasons, we can make it. > Storage work would have to be backported, but that can be mostly
and merge https://gerrit.ovirt.org/96631 that trivial
> if an initial master-merge rush is avoided. > > Thanks, > Milan
-- Anton Marchukov Team Lead - Release Management - RHV DevOps - Red Hat
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o. _______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-leave@ovirt.org Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/HVBZ4UAZGGSARW...
-- Martin Perina Associate Manager, Software Engineering Red Hat Czech s.r.o.
participants (4)
-
Anton Marchukov -
Dan Kenigsberg -
Martin Perina -
Milan Zamazal