Bug 68382 (cairo-1.14) - 1.14 tracker
Summary: 1.14 tracker
Status: NEW
Alias: cairo-1.14
Product: cairo
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Chris Wilson
QA Contact: cairo-bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on: 28145 56349 57094 59098 59173 59817 63203 63461 65626 67505 69380 69796 75705 78339 cairo-1.12 48784 53121 56981 58061 58726 58727 60852 63257 63633 63787 66218 67674 72244 73038 73901 74779 74894 77060 77298 89232
Blocks: cairo-1.16
  Show dependency treegraph
 
Reported: 2013-08-21 12:56 UTC by Uli Schlachter
Modified: 2016-04-06 13:52 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uli Schlachter 2013-08-21 12:56:59 UTC
Just some tracker for bugs which should be handled.
Comment 1 Bryce Harrington 2014-09-16 19:04:54 UTC
A number of these bugs have patches with them.

Bug 85688 - Is simply enlarging the fallback surface the right fix?

Bug 56981 - Uli proposed three fix options, but need a decision which to do.

Bug 63461 - Platform endian bug.  Fix LGTM.

Bug 67505 - Needs a bit of finishing

Bug 74779 - Needs thorough review

Bug 78339 - Thin line problem.  Two patches proposed, but need review.

Bug 78339 - Test case for cairo-test-suite needs integrated.  Underlying bug may need additional analysis and fixing.
Comment 2 Bryce Harrington 2014-09-16 19:12:02 UTC
I think we could postpone these bugs to a future milestone.  My logic is, they're uncommon situations, aren't crashes, and will need deeper analysis than we're likely to have time for before the release.

54991 - rendering bug; needs repro case

55836 - API changes being requested

60496 - rendering bug; needs repro case

62606 - packaging issue, but WFM so not really a blocker

So, in the interest of narrowing our focus I think we should move these four to the next milestone tracker bug.


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.