1.9.2 release

[JeroenDeDauw]

Target: weekend of April 12th

• Finish items under the milestone
• Finalize rel notes
• Update version number
• Create tag
• Create tarballs
• Update release template
• Announce on wiki
• Announce via mail
• Run composer update for smw.o
• Do a release tweet on Twitter

[JeroenDeDauw]

Any thoughts on when to do this? It's been two months now since the last feature release, so I'm thinking doing this in the next week or so would not be bad. We accumulated a bunch of stuff already after all. Still 8 open things that are filed under the 1.9.2 milestone, though probably most of them can just as well be bumped to the next one if they cannot be resolved soonish.

[JeroenDeDauw]

@mwjames @kghbln Thoughts?

[mwjames]

I'm fine with the schedule therefore Saturday sounds reasonable.

[kghbln]

No probs. I guess to allow for a week of testing is fine.

[mwjames]

1.9.2 deploys the new JSON i18n shim but it should only be released after "JSON i18n shim: Only register LocalisationCacheRecache handler once" has been merged and updated on SMW.

[JeroenDeDauw]

has been merged and updated on SMW.

We will need to do a follow up for that gerrit change?

[JeroenDeDauw]

@mwjames Any blockers from your side, or is the rel now fine to go?

[mwjames]

👍

[JeroenDeDauw]

Ok, will ignore the i18n thing than

[JeroenDeDauw]

@kghbln Feel like doing the next 3 steps? Than I'll take care of the remaining ones

[kghbln]

Yeah, will do so in about two or three hours / Done, though the docu on the wiki will need more fluff. Hope to do it tomorreow! @JeroenDeDauw

[kghbln]

I guess we need another composer update on smw.o to get the release notes displayed.

[JeroenDeDauw]

I guess we need another composer update on smw.o to get the release notes displayed.

Those two things are not related. I don't know why the thing is not displaying. Suspect it is a markdown rendering issue.

[kghbln]

I had hoped it would. There seems to be something within the file causing the rendering issue. All the others are showing up. However the wiki is fluffed up and updated now.

[JeroenDeDauw]

Funnily enough, this one is showing

{{#github:docs/RELEASE-NOTES.md}}

Perhaps it is a caching issue in the GitHub extension then - with the cache time not being set properly.

[mwjames]

JSON i18n shim performance issue

Fixed with https://gerrit.wikimedia.org/r/#/c/128830/1

[kghbln]

I think this should be in the 1.9.2.1 release. Except for the e-mail and twitter everything is already done for 1.9.2.

[mwjames]

I think this should be in the 1.9.2.1 release

Please no more 1.9.x.x releases, this just breaks the http://semver.org/ convention.

[kghbln]

Fair enough. So this will be in 1.9.3?

[JeroenDeDauw]

We will be semver compliant as of 2.0. Until then it only makes sense to our current scheme, which is essentially semver with a "1." prefix. Changing this in the middle of a release sequence does not seem like a good idea to me.

[JeroenDeDauw]

Well, since master only has fixes so far, we can simply tag 1.9.2.1. Shall we go with that?

[mwjames]

we can simply tag 1.9.2.1. Shall we go with that?

Fine by me.

#282 has been merged and it would allow me to clean-up the SESP\PropertyRegistryTest due to #279 issue (before the SESP\1.2.0 release).