On Tue, Oct 30, 2012 at 8:10 AM, Mark A. Hershberger mah@everybody.org wrote:
Unless something comes up, I don't see a reason why the RC2 release shouldn't be the 1.20 release.
One bug that was fixed since the RC2 release is Bug 40641 - "Links to COPYING and CREDITS on Special:Version should not trigger a download dialog"
There is a work-around for this, though, so I'm not sure it *needs* to be in 1.20.
Since someone at WMF still needs to make the official release, I guess all that is left is to ask Sam to make an announcement. We can just squeeze the release into October.
Hi Mark,
I think it would make more sense for you to make the announcement than someone here, if you're up for it. We'll just need to get your key in the right place, and it'd be nice for someone here to have the opportunity to review what you're posting, but there's no reason (that I can see) why you can't be the one to send it.
The only thing that is necessarily a WMF function is placing the final tarball in the right spot. That's something that I don't think even Sam has the rights for; it's traditionally been an ops function.
At the risk of hijacking the thread, I'll say this. For 1.21, I would love for the tarball creation process to be something that we can do from Jenkins, such that the final manual copy step is something that goes from our Jenkins host, rather than a tarball produced on a particular developers machine.
Rob