In the good old days (some months ago), we didn’t have to use revision numbers when releasing new localised WordPress versions. I’ll be blunt: Why do we have to use revision numbers? It’s a source of errors and some frustration. Can’t we go back to the way it was before?
-
frilyd
Reply
frilyd, 
Zé, and 2 others are discussing. 
WP Polyglots 
Xavier 3:12 pm on May 2nd, 2011 Permalink |
I’ve never had to do that. Revision numbers are for those who cannot wait for the building tool to feature the real version number, methinks.
Peter 4:56 am on May 3rd, 2011 Permalink |
So you always use “HEAD”, or what?
frilyd 6:39 pm on May 3rd, 2011 Permalink |
I tried (around the release of 3.1, I think) to just use the automatic values. That gave me 3.2-bleeding, in en_US, which is not what I want. Later, I released using revision numbers, which has sort of worked until now. Lately, users have reported that they can’t update to the new nn_NO version from the dashboard. My last release was according to https://wppolyglots.wordpress.com/2011/04/26/you-can-use-revision-17712-to-compile-your/#comment-2218 .
I’ll try to release without revision numbers, and see what happens. If it ruins my test installation, I’ll delete that release.
Zé 10:59 pm on May 3rd, 2011 Permalink |
Remember that you don’t need to release to test, you can download an unreleased build from the dashboard.
frilyd 11:32 am on May 4th, 2011 Permalink |
That of course is an alternative. I can try that first, and then (if it works) release it and see if it also works via dashboard upgrading. Thanks. Will report back.
Referring to this post today I tried building… « WP Polyglots 8:22 am on May 24th, 2011 Permalink |
[…] to this post: today I tried building nn_NO from Rosetta without using revision numbers (project 3.1 and 3.1.x). […]