On Fri, Mar 16, 2018 at 8:40 AM, Juan A. Suarez Romero <jasua...@igalia.com> wrote: > Nominated means that these patches does not enter in this release due they > arrived a bit late, but they are proposed to cherry-pick them for the next > release (in 1 or 2 weeks). > > The reason is that some days before this pre-announcement is sent, we close > the > list of patches that enter in the release, and we do a lot of testing to > verify > nothing is broken). If there's some regression, we just try to fix them. And > when everything is ready, we send the pre-announcement email. > > The nominated patches are those that arrive after we close the list, and we > are > under the testing process. As we don't want to restart the full process again > and again, we just nominate them for the next release. Otherwise that would > delay the release too much.
Why not send the pre-announcement right when it's closed? Since your testing doesn't cover all drivers, shouldn't everyone just be able to test at the same time, and then be able to add to the existing list with additional fixes (or removals of picked commits)? _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
