[cairo] Release?

[Bryce W. Harrington]

On Tue, Feb 04, 2014 at 10:40:30PM +0100, Uli Schlachter wrote:
> Hi,
> 
> 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
> CAIRO_MIME_TYPE_JBIG2{,_GLOBAL,_GLOBAL_ID}.
> 
> 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?

Yeah, probably better to cherrypick out the known-good bugfixes for a
stable 1.12.7 release.

master is currently in fairly good shape (there's not a huge amount
changed since 1.12), but I think it could benefit from further cleanup
before release.

Bryce