On 22-06-11 02:32, Krzysztof KosiĆski wrote:
2011/6/21 Jasper van de Gronde <th.v.d.gronde@...528...>:
On the other hand, if the cairo branch only has very minor problems when used with the "old" cairo and/or the "new" cairo is generally usable, then what's the problem?
The "new" Cairo (1.11.2) is rather stable - I have used it on my desktop for several weeks and it hasn't caused me any problems. I have added it to Windows devlibs before merging.
I wouldn't describe the problems with "old" Cairo (1.10.2) as very minor - on large drawings the gradients will disappear at a certain zoom level. A radial gradient that fills an A4 page will disappear at around 400% zoom. Furthermore, large gradients will not line up correctly with their stops.
Then, as far as I'm concerned I would recommend trying to get the Cairo branch in asap, put the "new" cairo in devlibs, celebrate and see what happens. If there is some major defect that didn't come up till now it probably won't come up until we put it out in the "wild" (among developers) anyway, and then we should have enough time before the next release to decide what we're going to do about it.
As was mentioned before by others, to facilitate point releases and such it might not be a bad idea to branch devlibs in the same way as is done with trunk.
Looking forward to the cairo branch being merged in trunk :)