[cairo] Release?

Uli Schlachter psychon at znc.in
Tue Feb 4 22:40:30 CET 2014


On 04.02.2014 22:21, Behdad Esfahbod wrote:
> On 14-02-04 03:16 PM, Uli Schlachter wrote:
>> On 04.02.2014 19:15, Behdad Esfahbod wrote:
>>> Can you please roll a cairo release?
>> There is the cairo-1.14 tracker bug in bugzilla:
>> https://bugs.freedesktop.org/show_bug.cgi?id=cairo-1.14
>> I don't really think of those bugs as release blockers, but more as "someone
>> should look at this before a release". However, the summary seems to be
>> "cairo-win32 is broken and unmaintained(!!)", "lots of random small bugs that
>> someone might want to look at", "GTK's HiDPI scaling will be broken on Mac OS
>> (bug 69796)" and "--enable-xlib-xcb is broken (bug 67505)".
>> Again: I don't think of these as release blockers, I just want someone else to
>> think about whether cairo master is in a releasable state.
> Quickly browsing through the commits in master since 1.12.6, look mostly like
> general bugfixes not worthy of 1.14 but a followup minor release.

We have new public APIs:

$ git log -p 1.12.6.. $(ls src/*.h | grep -v private.h | grep -v inline.h | grep
-v cairoint.h)

This is cairo_egl_device_get_{display,context}(),
cairo_surface_[gs]et_device_scale(), CAIRO_STATUS_JBIG2_GLOBAL_MISSING and

All of these are currently documented as "since 1.14".

This is actually less than I expected. I guess we could make an 1.12 branch and
hide/remove these API additions and then do a release. Or are we allowed to add
new APIs in micro releases?

- Captain, I think I should tell you I've never
  actually landed a starship before.
- That's all right, Lieutenant, neither have I.

More information about the cairo mailing list