| Summary: | [TRACKER] Mesa 19.2 release tracker | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | Emil Velikov <emil.l.velikov> |
| Component: | Other | Assignee: | mesa-dev |
| Status: | REOPENED --- | QA Contact: | mesa-dev |
| Severity: | normal | ||
| Priority: | medium | CC: | clayton.a.craft, denys.kostin, emil.l.velikov |
| Version: | unspecified | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
| Bug Depends on: | 110295, 110395, 110765, 110814, 111038, 111069, 111339, 111384, 111405, 111450, 111454, 111493, 111522, 111527 | ||
| Bug Blocks: | |||
|
Description
Emil Velikov
2019-08-20 22:34:49 UTC
Emil, please review this ticket according to "blocking" for release. Pavlo sent a question according to it about 3 weeks ago, in the mailing threads, but possibly it was lost. https://bugs.freedesktop.org/show_bug.cgi?id=110814 - this ticket is regression from 19 mesa version, there is a patch, which fixed an issue (me and reporter tested it, but would be great to review it and merge, if it is ok) -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/947. See also the 19.2 release milestone in gitlab: https://gitlab.freedesktop.org/mesa/mesa/-/milestones/1 I thought we were going to leave the 19.2 tracker bugs in bugzilla until after the release. The migration of this bug doesn't hurt the release, because we can still see the list of bugs that need to be resolved. I don't think we can adequately reference unmigrated bugzilla bugs in the gitlab milestone. We should still use this tracker to gate the release, in spite of the migration. Apologies, didn't intend to close this in the migration. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.