[cairo] 1.10 release schedule
behdad at behdad.org
Tue Jan 12 17:32:44 PST 2010
On 01/12/2010 08:11 PM, Carl Worth wrote:
> Yes. Thanks Benjamin, Behdad and Chris for helping get this discussion
Hi Carl. Well, good to hear from you!
> I'd like to help fix that, and will be happy to jump in and do what I
> can here. I'd also feel fine if Chris wanted to take the
> release-management task on himself. But I know that when I was doing
> most of the cairo development, I often wished there was someone else to
> say "No, it's too late for that code. It's time to release." So, I'll be
> glad to be that "someone else" for Chris now if that would be useful.
If you can be forced to do that, I'd really love to see you just do it since I
think you're a great release manager (even if your reverts have left some hard
feelings in me ;) ). Failing that, I'd suggest Benjamin or Joonas (in that
order) do it.
> Major version Release date Delta since previous major release
> ------------- ------------ ----------------------------------
> cairo 1.0.0 2005-08 -- ------
> cairo 1.2.0 2006-07 11 months
> cairo 1.4.0 2007-03 8 months
> cairo 1.6.0 2008-04 13 months
> cairo 1.8.0 2008-09 5 months
> cairo 1.10.0 2010-?? ? >16 months
> I don't know if regular 6-month (or 12-month) releases would be better
> for cairo. But it's clear that no matter how soon we release cairo 1.10
> it will have been a longer delta than anything previous.
It also is kind of a sign of maturity. I think our biggest failure this cycle
was NOT not getting 1.10 out "on time". It was not getting a next 1.8.x
> I definitely want to use cairo's current master branch as the basis of
> the new release, and get things in releasable shape as soon as possible.
> That can mean that cleaned-up portions of Chris's giant branch can land,
> but I don't want to commit to necessarily having it all land.
Lets move in the "only bug fixes in" mode already.
> The two things I'd like to use to track our progress toward something
> releasable are:
> 1. The cairo-1.10 tracking bug:
> I proposed this last October. Adrian has added some useful
> regressions to it. I strongly encourage anyone else to add any other
> bugs they are aware of that really should be fixed.
> 2. The cairo test suite
> I honestly haven't run this much recently. It was my intention when I
> originally created it that the master branch would basically always
> be kept in a test-suite-clean state (or something close to that). I'm
> nervous that we've strayed from that.
> To the extent that existing side branches address either of these goals,
> I will be encouraging people to get those branches merged to cairo
> Does the above sound reasonable to everyone?
Sure. Nothing controversial.
> I'm certainly looking forward to becoming much more active in cairo
> development again. It should be a lot of fun!
More information about the cairo