1.3.0 release planning

[jfritschi]

I was planning on doing the 1.3.0 release somewhere in the near future since we are pretty much done with all the major issues i think. My soft target would be end of february.

The only open topic is the log dir issue #22 but there is little work to be done except to investigate the php docs. The other 2 issues that are earmarked for 1.3 are more unit test #6 and the few remaining style warnings #14. I guess we can postpone them for a later release since they offer no functionality for the end user anyway.

The only open work is the Changelog, an Upgrading doc and writing a release announcement. Is there anything else missing that needs to be done?

@adamfranco: Any objections or comments?

[adamfranco]

I think we have a pretty solid release ready. I agree that #6 and #14 can just be left for later improvement in either a 1.3.x release or any other future release when we get to them. I can't think of any reason to wait any longer. Would you like to release an RC as soon as #22 is ready and then wait a few weeks before tagging the 1.3.0 release?

[jfritschi]

Yes, my plan was to tag the RC as soon as #22, Changelog and some Upgrading docs are done.

I have some more spare time on the weekend which will probably give me a chance to finish all this work.

[jfritschi]

I have published the release.

[jfritschi]

All done, release announcement is out.