1.9.x branch policy

[Jeremy Huddleston]

So, 1.9.0 is out the door, and I'm the sucker who volunteered to take over for Peter as stable release manager for this cycle. =)

I just pushed a server-1.9-branch to origin (it's just 1.9.0... which is the same as master, so don't get too excited).

I intend to follow a 6 week release cycle for 1.9.1 and 1.9.2 (this will likely change to an 8 week cycle for 1.9.3 and 1.9.4):
    rc1 will follow 3 weeks after a release
    rc2 will follow 2 weeks after that
    final will be 1 week after rc2

Commit policy for 1.9 will be pretty much the same as it was for 1.8.  Changes intended for 1.9.x must first land in master.  Once they settled in master, you can nominate them for 1.9 by replying to the original patch email, CC-ing me, and updating the subject line to contain "[PATCH 1.9]".  If you have multiple changes, you should create a local branch on your people.freedesktop.org repository and send a pull request to me (and CC the list) with "[PULL 1.9]" in the subject line.  Make sure you 'cherry-pick -x' into your local branch to keep a reference to the original patch in master.

During the 1 week leadup to release after rc2, only regressions over the previous stable release will be accepted.

This policy is also available on the wiki: http://www.x.org/wiki/Server19Branch

This means 1.9.1rc1 (1.9.0.901) will be out around September 10

Thanks,
Jeremy