Quoting Juan A. Suarez Romero (2018-06-19 00:08:27) > On Fri, 2018-06-15 at 09:36 -0700, Dylan Baker wrote: > > Quoting Juan A. Suarez Romero (2018-06-15 07:26:18) > > > On Thu, 2018-06-14 at 10:16 -0700, Dylan Baker wrote: > > > > Quoting Bas Nieuwenhuizen (2018-06-14 09:21:49) > > > > > On Thu, Jun 14, 2018 at 6:13 PM, <dy...@pnwbakers.com> wrote: > > > > > > Hello list, > > > > > > > > > > > > The candidate for the Mesa 18.1.2 is now available. Currently we > > > > > > have: > > > > > > - 42 queued > > > > > > - 6 nominated (outstanding) > > > > > > - and 0 rejected patches > > > > > > > > > > > > Notable changes in this release: > > > > > > - numerous fixes for radv > > > > > > - libatomic checks for meson, as well as fixing coverage for less > > > > > > common (not > > > > > > arm or x86) platforms > > > > > > - lots of common Intel fixes > > > > > > - GLX fixes > > > > > > - tarball fixes for android > > > > > > - meson assembly fixes for x86 when doing an x86 -> x86 cross > > > > > > compile > > > > > > > > > > > > Take a look at section "Mesa stable queue" for more information. > > > > > > > > > > > > > > > > > > Testing reports/general approval > > > > > > -------------------------------- > > > > > > Any testing reports (or general approval of the state of the > > > > > > branch) will be > > > > > > greatly appreciated. > > > > > > > > > > > > The plan is to have 18.1.2 this Friday (June 13th), around or > > > > > > shortly after 10 > > > > > > AM PDT. > > > > > > > > > > June 15th? > > > > > > > > Yes, June 15th. > > > > > > > > Apparently being woken up at 5AM does more brain damage than I thought. > > > > > > Also, we usually wait 48h (two days) between the pre-announcement and the > > > final > > > release, to give more time for testing. > > > > > > > > > J.A. > > > > > > > I don't even understand why we make these announcements TBH. I have a public > > 18.1-proposed branch that I push to *every weekday*. > > > Out of curiosity, any reason to keep the proposed branch in your personal > repository, instead of in main Mesa repo? > > > I thought the proposal was to have those proposed/wip branches in the main > repository, so everybody is aware were they are, no matter who is in charge of > the release. > > > J.A. > > > Anyone can pull that branch > > *anytime* to get the latest version. The only thing the announce email > > really > > serves AFAICT, is to say "the staging/proposed branch has been merged to the > > release branch". I don't think that's all that interesting TBH. > > > > Dylan
I just remembered that you can set two push remotes for a single branch, so I think I'll add a staging/18.1 branch to master as a second remote and push to that as well. Do you like that name, or would you prefer something different? Dylan
signature.asc
Description: signature
_______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
