<div dir="ltr">Sorry for the late breaking hold but I just realized that GL_ARB_gl_spirv and OpenGL 4.6 for Intel is 1 regression (I think it's not even a regression) away from landing. Can I have 24 hours?<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Aug 19, 2019 at 10:30 AM Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com">emil.l.velikov@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sunday, 18 August 2019, Matt Turner <<a href="mailto:mattst88@gmail.com" target="_blank">mattst88@gmail.com</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Thu, Aug 8, 2019 at 2:56 AM Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com" target="_blank">emil.l.velikov@gmail.com</a>> wrote:<br>
><br>
> On Wed, 7 Aug 2019 at 21:43, Mark Janes <<a href="mailto:mark.a.janes@intel.com" target="_blank">mark.a.janes@intel.com</a>> wrote:<br>
> ><br>
> > Eric Engestrom <<a href="mailto:eric@engestrom.ch" target="_blank">eric@engestrom.ch</a>> writes:<br>
> ><br>
> > > On 2019-07-31 at 09:38, Emil Velikov <<a href="mailto:emil.l.velikov@gmail.com" target="_blank">emil.l.velikov@gmail.com</a>> wrote:<br>
> > >> Hi all,<br>
> > >><br>
> > >> Here is the tentative release plan for 19.2.0.<br>
> > >><br>
> > >> As many of you are well aware, it's time to the next branch point.<br>
> > >> The calendar is already updated, so these are the tentative dates:<br>
> > >><br>
> > >> Aug 06 2019 - Feature freeze/Release candidate 1<br>
> > >> Aug 13 2019 - Release candidate 2<br>
> > >> Aug 20 2019 - Release candidate 3<br>
> > >> Aug 27 2019 - Release candidate 4/final release<br>
> > >><br>
> > >> This gives us around 1 week until the branch point.<br>
> > >><br>
> > >> Note: In the spirit of keeping things clearer and more transparent, we<br>
> > >> will be keeping track of any features planned for the release in<br>
> > >> Bugzilla [1].<br>
> > >><br>
> > >> Do add a separate "Depends on" for each work you have planned.<br>
> > >> Alternatively you can reply to this email and I'll add them for you.<br>
> > >><br>
> > >> [1] <a href="https://bugs.freedesktop.org/show_bug.cgi?id=111265" target="_blank">https://bugs.freedesktop.org/show_bug.cgi?id=111265</a><br>
> > ><br>
> > > Thanks!<br>
> > ><br>
> > > As per previous discussions (I don't remember where, sorry) as well as<br>
> > > internal discussions, I think we should add all currently open<br>
> > > regressions since 19.1 as blockers for this release.<br>
> ><br>
> > My understanding is that the "feature tracker" blocks the creation of<br>
> > the release branchpoint. A separate "release tracker" blocks the<br>
> > release of 19.2.0. Unfixed regressions go on the "release tracker", not<br>
> > the "feature tracker". We backport bug fixes to release branches, but<br>
> > we don't backport features.<br>
> ><br>
> Yes that is correct. We are interested in features for the next few days.<br>
> Afterwords we'll focus on bugfixes.<br>
<br>
The last bug in the feature tracker was closed on the 14th. Can we make RC1 now?<br>
</blockquote><div><br></div><div>Hi Matt,</div><div><br></div><div>Sure thing. I'm about to board the plane in a few minutes, I'll roll RC1 first thing tomorrow morning.</div><div><br></div><div>Thanks</div><div>Emil</div><div>P.S. Pardon the html formatting</div>
_______________________________________________<br>
mesa-dev mailing list<br>
<a href="mailto:mesa-dev@lists.freedesktop.org" target="_blank">mesa-dev@lists.freedesktop.org</a><br>
<a href="https://lists.freedesktop.org/mailman/listinfo/mesa-dev" rel="noreferrer" target="_blank">https://lists.freedesktop.org/mailman/listinfo/mesa-dev</a></blockquote></div>