[ACTION REQUIRED] stabilization branches for 4.1
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th. oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET). -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
A gentle reminder On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th.
oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET).
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
--Apple-Mail=_4E0B64D3-9A97-4886-B9F4-928394B8A783 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 I suggest to review the repo configuration for CI and lago, at least for = vdsm It=E2=80=99s using various repos, it=E2=80=99s quite a mess And broken for ppc64le Any help reviewing it from someone who knows how it should look like = would be appreciated Thanks, michal
On 15 Dec 2016, at 15:33, Sandro Bonazzola <sbonazzo@redhat.com> = wrote: =20 A gentle reminder =20 On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo@redhat.com = <mailto:sbonazzo@redhat.com>> wrote: In order to stabilize the build and allow to prepare jenkins on time, = 4.1 branches need to be created before or on Monday Dec 19th. =20 oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time = (10:00 AM CET). =20 --=20 Sandro Bonazzola Better technology. Faster innovation. Powered by community =
collaboration. > See how it works at redhat.com <http://redhat.com/> >=20 >=20 > --=20 > Sandro Bonazzola > Better technology. Faster innovation. Powered by community = collaboration. > See how it works at redhat.com = <http://redhat.com/>_______________________________________________ > Infra mailing list > Infra@ovirt.org > http://lists.ovirt.org/mailman/listinfo/infra
--Apple-Mail=_4E0B64D3-9A97-4886-B9F4-928394B8A783 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 <html><head><meta http-equiv=3D"Content-Type" content=3D"text/html = charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; = -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" = class=3D"">I suggest to review the repo configuration for CI and lago, = at least for vdsm<div class=3D"">It=E2=80=99s using various repos, = it=E2=80=99s quite a mess</div><div class=3D"">And broken for = ppc64le</div><div class=3D"">Any help reviewing it from someone who = knows how it should look like would be appreciated</div><div = class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div = class=3D"">michal<br class=3D""><div class=3D""><br = class=3D""><div><blockquote type=3D"cite" class=3D""><div class=3D"">On = 15 Dec 2016, at 15:33, Sandro Bonazzola <<a = href=3D"mailto:sbonazzo@redhat.com" class=3D"">sbonazzo@redhat.com</a>>= wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div = dir=3D"ltr" class=3D"">A gentle reminder<br class=3D""><div = class=3D"gmail_extra"><br class=3D""><div class=3D"gmail_quote">On Mon, = Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <span dir=3D"ltr" = class=3D""><<a href=3D"mailto:sbonazzo@redhat.com" target=3D"_blank" = class=3D"">sbonazzo@redhat.com</a>></span> wrote:<br = class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 = .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr" = class=3D""><div style=3D"font-size:12.8px" class=3D"">In order to = stabilize the build and allow to prepare jenkins on time, <span = style=3D"background-color: transparent; font-family: arial; font-size: = 14.6667px; font-weight: 700; white-space: pre-wrap;" class=3D"">4.1 = branches need to be created before or on Monday Dec = 19th.</span></div><div style=3D"font-size:12.8px" class=3D""><br = class=3D""></div><span style=3D"font-size:12.8px" class=3D"">oVirt = engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 = AM CET).</span><span class=3D"HOEnZb"><font color=3D"#888888" = class=3D""><div style=3D"font-size:12.8px" class=3D""><br = class=3D""></div>-- <br class=3D""><div = class=3D"m_3895549614964894451gmail_signature"><div dir=3D"ltr" = class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div = class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><div dir=3D"ltr" = class=3D"">Sandro Bonazzola<br class=3D"">Better technology. Faster = innovation. Powered by community collaboration.<br class=3D"">See how it = works at <a href=3D"http://redhat.com/" target=3D"_blank" = class=3D"">redhat.com</a></div></div></div></div></div></div></div></div> </font></span></div> </blockquote></div><br class=3D""><br clear=3D"all" class=3D""><div = class=3D""><br class=3D""></div>-- <br class=3D""><div = class=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div = dir=3D"ltr" class=3D""><div class=3D""><div dir=3D"ltr" class=3D""><div = class=3D""><div dir=3D"ltr" class=3D""><div class=3D""><div dir=3D"ltr" = class=3D"">Sandro Bonazzola<br class=3D"">Better technology. Faster = innovation. Powered by community collaboration.<br class=3D"">See how it = works at <a href=3D"http://redhat.com/" target=3D"_blank" = class=3D"">redhat.com</a></div></div></div></div></div></div></div></div> </div></div> _______________________________________________<br class=3D"">Infra = mailing list<br class=3D""><a href=3D"mailto:Infra@ovirt.org" = class=3D"">Infra@ovirt.org</a><br = class=3D"">http://lists.ovirt.org/mailman/listinfo/infra<br = class=3D""></div></blockquote></div><br = class=3D""></div></div></body></html>= --Apple-Mail=_4E0B64D3-9A97-4886-B9F4-928394B8A783--
On Thu, Dec 15, 2016 at 5:30 PM, Michal Skrivanek < michal.skrivanek@redhat.com> wrote:
I suggest to review the repo configuration for CI and lago, at least for vdsm It’s using various repos, it’s quite a mess And broken for ppc64le Any help reviewing it from someone who knows how it should look like would be appreciated
I hope not being the only one :-) Anyway, I'll try to go over it, please ping me tomorrow morning, we can go over it together.
Thanks, michal
On 15 Dec 2016, at 15:33, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
A gentle reminder
On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th.
oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET).
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
A gentle reminder branching will happen in 1 hour On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th.
oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET).
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
ovirt-engine 4.1 branch has been created. On Mon, Dec 19, 2016 at 8:56 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
A gentle reminder branching will happen in 1 hour
On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th.
oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET).
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
Hi, maybe I've not made myself clear enough about stabilization branching, but it should have happened yesterday as deadline. I may understand that projects which are not under heavy development like otopi or optimizer or external scheduler will keep master until they really start looking iinto 4.2 but I would expect projects like vdsm branching and enter bugfix only mode. Still, I don't see ovirt-4.1 branch there and patches being merged without bug-url pointing to 4.1 bugs. Can we please stabilize vdsm? We have scheduled beta2 tomorrow morning at 11:00 TLV time. On Mon, Dec 19, 2016 at 10:00 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
ovirt-engine 4.1 branch has been created.
On Mon, Dec 19, 2016 at 8:56 AM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
A gentle reminder branching will happen in 1 hour
On Mon, Dec 12, 2016 at 3:42 PM, Sandro Bonazzola <sbonazzo@redhat.com> wrote:
In order to stabilize the build and allow to prepare jenkins on time, 4.1 branches need to be created before or on Monday Dec 19th.
oVirt engine will be branched on Monday Dec 19th at 11:00 AM TLV time (10:00 AM CET).
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
-- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com
participants (2)
-
Michal Skrivanek -
Sandro Bonazzola