When I build a the new 3.1.1 version now and choose the following in Rosetta:
Locale branch: Tags/ 3.1.1
Project 3.1 and 3.1.x
WordPress Revision: HEAD
WordPress version: 3.1.1
I end up with a 3.1.2-alpha version which obviously is not what I should be getting. Is there a way to select to get the 3.1.1 tag from SVN?
herzcthu 8:48 am on April 6, 2011 Permalink |
I used WP revision number 17609 and it is OK. But Emre said 17595 to use. So change your revision to 17609 or 17595.
Remkus de Vries 8:52 am on April 6, 2011 Permalink |
That did the trick. Was not aware we could choose the version in that manner. I had tried to enter revision numbers there before but I always got an error. Works now, so thanks!
Emre Erkan 10:04 pm on April 6, 2011 Permalink |
You can always check tags for revision numbers: http://core.trac.wordpress.org/browser/tags
It’s the safest way to make things right for now.
Ran Yaniv Hartstein 12:08 pm on April 6, 2011 Permalink |
3.1.1 was tagged in 17595 – so this is the version number to use.
http://core.trac.wordpress.org/changeset/17595
I had the same issue with he_IL – with project 3.1 and 3.1x and revision HEAD gives me “3.1.2-alpha” as version. Releasing like this, even if you override the version number manually (enter 3.1.1) under version) would still release witg 3.1.2-alpha in version.php, and would show a bleeding update notice to all users.
Setting the revision to 17595 seems to solve this issue.