[cairo] Upcoming release schedule

[Adrian Johnson]

On 14/06/17 11:18, Bryce Harrington wrote:
> On Mon, Jun 12, 2017 at 04:44:38PM -0700, Bryce Harrington wrote:
>> On Sat, Jun 10, 2017 at 02:43:00PM +0200, Uli Schlachter wrote:
>>> On 09.06.2017 09:20, Bryce Harrington wrote:
>>>> Just a head's up that I'll be rolling a new snapshot next week.
>>>>
>>>> There's not too terribly much on trunk, but it's been 6 months so figure
>>>> we're due.  This'll just be a quickie snapshot, version 1.15.6.  I plan
>>>> on posting it by Tuesday.
>>>>
>>>> While I'm at it, I can also roll stable bugfix point releases for the
>>>> 1.14.x and 1.12.x trees, although there are currently no commits on
>>>> either branch.  If you have bugfix patches suitable for inclusion in the
>>>> stable releases please either cherrypick them to one or both branches,
>>>> or flag the patches for me so I can cp them.  I plan to cut the releases
>>>> for these by Thursday.
>>>
>>> Thanks for handling these!
>>>
>>> I cherry-picked my recent fix to the 1.14 branch.
>>
>> Cool thanks.
>>
>>> However, the last 1.12
>>> release was in 2014 and I do not see why a new release from that branch
>>> should be done, so I skipped that.
>>
>> Yeah, fair enough.  I am figuring that stuff cp'able to 1.14 may also
>> apply to 1.12 without change, so opportunity cost of a point release
>> there could be low.  I know it's old, but I also know there are still
>> users of the old releases -- cairo snapshots exist in various web
>> browser, etc. trees.  Anyway, I'll play it by ear whether to do 1.12,
>> thanks for giving it consideration.
>>
>>> I'm not sure if just this one patch is worth a release. I see some
>>> commits from others (Adrian?) that might be worth cherry-picking as
>>> well, but I don't have the time to look too closely at this currently.
>>
>> I'd spotted a few other patches in addition to yours I thought could be
>> picked easily, which I'll do today or tomorrow as time permits.
>> Admittedly this release is going to be pretty light.
> 
> Uli, your XSync patch looks like it might be pertinent to include?
> 
> Other than that there's a couple doc updates relating to bug #99094
> 
> All the above cp cleanly to 1.12.
> 
> I've not had a chance to look close enough at Adrian's patches either;
> at least some are building atop the pdf feature work that isn't in the
> 1.14 tree but I think some could be worth inclusion.  Advice would be
> appreciated.

The following are bug fixes that don't depend on new feature work:

ebdb59f836d2011f0f193b432114dfde68c40c6a
87491030e4a8c77c386d1e9bcc0473513d039907
5cd14e4a2b6d6f65344561384c6b3859b04a6eb4
bc3b4b5377a92d1a1ede0a73996cf7d1b931f9aa
f8cf7d00a3334d72f0dc635ea740b0b3dfe6e15c
c8c48714a22d42314217ef40ecd62d9dd2384562
9aab4083b89f9c3c903a31c33b2c714c97677b0c
511777c60ded59ae9b0d76f1df422fbd4dbcb4e3

There is also this bug that I had forgotten about:

https://lists.cairographics.org/archives/cairo/2017-March/027898.html


> 
> Bryce
>