Otto gave me a heads up that some download packages aren’t being packaged against the 3.1.1 tag, but rather the 3.1 branch. This is resulting in the es_ES download actually being version 3.1.2-alpha. I imagine this affects multiple locales.
This is not good. While our branches are always going to be quite stable, as we’re very cognizant of them being run in production, it’s a huge issue for users, as it causes confusion and perception problems.
Please test your builds. I’m not familiar enough with the deployment system to know where things went wrong (or if it was a systems error, rather than human error) or how to fix it, but I imagine Zé can provide some further direction.
Mattias Tengblad 6:16 am on April 11, 2011 Permalink |
This is when glotpress is used as the base for translations creating packages.
Remkus de Vries 6:19 am on April 11, 2011 Permalink |
I had the same issue with the nl_NL where Rosetta at first didn’t pick up the proper tag, as discussed here but 30 minutes later it all worked perfectly.
Andrew Nacin 6:21 am on April 11, 2011 Permalink |
Yes, I figured that was the issue. I imagined that Rosetta was similar to our own release deployment system, such that it allows you to specify trunk, branch, or tag, as well as a revision. We should probably just restrict packaging to tags and HEAD.
Remkus de Vries 6:25 am on April 11, 2011 Permalink |
Yea, that sounds like a plan. Will that still allow us to build betas and RC’s?
Zé 8:54 am on April 11, 2011 Permalink |
Those are either in a tag or trunk (HEAD), so, yes.
Andrew Nacin 8:56 am on April 11, 2011 Permalink |
You’d no longer be able to build development packages for point releases, but we typically don’t even announce those. I’ll add this to my list.
Remkus de Vries 8:58 am on April 11, 2011 Permalink
Point releases don’t usually bring new translatable strings so that fine.
Zé 8:59 am on April 11, 2011 Permalink
Mostly, but I wouldn’t bet on this
Remkus de Vries 9:01 am on April 11, 2011 Permalink
True, but none to the extend that it would valid the need for RC testing imo.
Zé 8:54 am on April 11, 2011 Permalink |
There was no system error that I can pinpoint. I’d also alert to the fact that ‘create a new tag/branch in svn > bulid > release’ in one go can also lead to this kind of error, i.e. the newly created tag/branch won’t appear immediately in the locale site, which makes it too easy to choose the wrong one. Hence I’d recommend creating the tag ahead of time. I also agree with excluding branches (both core and locale) from build options.
Andrew Nacin 8:57 am on April 11, 2011 Permalink |
Thanks a lot Zé. Is this the tag that’s created by us as part of our release process?
Are you able to force a new 3.1.1-es_ES build off the tag?
Zé 9:03 am on April 11, 2011 Permalink |
Yes. They’ll need to delete the current build and release and start over. Then warn users (on the es.wordpress.org blog, I suppose) that they’ll need to reinstall 3.1.1
Zé 9:06 am on April 11, 2011 Permalink |
Which reminds me that having a way to push messages to .org dashboards from the locale .org site would be a nice feature for the next iteration.
Andrew Nacin 9:07 am on April 11, 2011 Permalink
Use case? I don’t really see one here. We can’t even force messages yet, though we’re aiming to have that working soon.
Zé 9:09 am on April 11, 2011 Permalink
Unlike core, strings can have updates/corrections within the same release. It’d be nice to be able to point them to the updated language files, for instance.
Andrew Nacin 9:11 am on April 11, 2011 Permalink
Hmm. Interesting. If all goes well, I’d love to see language pack versioning completely supersede the need for that.
Andrew Nacin 9:08 am on April 11, 2011 Permalink |
Cool. To the es_ES maintainer(s), I’d personally prefer that any post simply emphasizes that the 3.1.2-alpha build is stable, so they can continue to simply use that, rather than do a pointless re-install. (Of course, let them know that they can do that if they wish.) It’d be good to acknowledge the mistake, but it didn’t cause an actual issue, just contributed to confusion and uncertainty. It’s trust and confusion that needs repairing, not actual sites.
Zé 9:12 am on April 11, 2011 Permalink
Which is exactly what we did for pt_PT when 3.0.5 was released as 3.1-RC4, but we still rebuilt and rereleased.
Andrew Nacin 9:15 am on April 11, 2011 Permalink
Well I’ll be dammed. A few of us examined logs and the API code tried our hardest to figure out why the heck some people were getting upgraded to 3.1. Turns out that’s what they were being given!
Zé 9:24 am on April 11, 2011 Permalink
Also, some people like to live dangerously…
Andrew Nacin 9:29 am on April 11, 2011 Permalink
Not typically by accident, though.
Remkus de Vries 9:13 am on April 11, 2011 Permalink
And what I did when I released the 3.1.2-alpha ..
Zé 12:07 pm on April 11, 2011 Permalink |
It’s both, actually (core and locale)
Stas Sușcov 10:01 am on April 12, 2011 Permalink |
I think the best would be to somehow inform everyone on new release, about the SVN revision they have to use when compiling the package. Me, for example can’t see the tags/branches since we do not use the SVN (except for dist/).
http://i.imgur.com/5H1qX.png
And yes, the best is to recompile the package with the correct revision.
They can also use my localize plugin to switch back to any version.
Zé 5:04 pm on April 12, 2011 Permalink |
When I mentioned the tags/branches not showing up, I meant the dropdown used to build from rosetta, independently of the fact that you’d be building from svn or GP. The revision idea is good, though.
Link to the plugin?
Stas Sușcov 7:37 pm on April 12, 2011 Permalink |
If the revision idea is acceptable, than, first who sees the release and can blog here, can post the update. I can also do this in future.
The plugin was already posted once here, it can be used to switch to any language from GP.
http://wordpress.org/extend/plugins/localize/
Zé 10:28 pm on April 12, 2011 Permalink |
Thanks for the link and also for volunteering to monitor the revision
Rafael Poveda - RaveN 8:05 pm on April 16, 2011 Permalink |
Sorry about that. The version 3.1.2-alpha in translate was corrected to 3.1.1 April the 11th.
The person who release the version did it without creating SVN, so there was a problem with versions, translations and all this stuff.
We are now writing a how to release a localized WP version and will be in codex very soon. We think it’s neccessary, because the proccess is not clear.
So sorry for not answering before.
Gabriel Reguly 2:16 am on July 13, 2011 Permalink |
Hi Rafael,
“We are now writing a how to release a localized WP version and will be in codex very soon. We think it’s neccessary, because the proccess is not clear.”
Very soon now?
Rafael Poveda - RaveN 6:42 am on July 13, 2011 Permalink |
It’s in my to-do list!
I hope to have some free time next week to do this.