[wp-meta] [Making WordPress.org] #1696: Automated release packages should update version number in readme.html

[Making WordPress.org]

#1696: Automated release packages should update version number in readme.html
-------------------------------------------+-----------------
 Reporter:  SergeyBiryukov                 |      Owner:
     Type:  defect                         |     Status:  new
 Priority:  normal                         |  Milestone:
Component:  International Sites (Rosetta)  |   Keywords:
-------------------------------------------+-----------------
 On i18n.svn.wordpress.org, translators can create an SVN branch for an
 upcoming release and commit a translated `readme.html` file to be used for
 [https://make.wordpress.org/polyglots/handbook/translating/packaging-
 localized-wordpress/automated-release-packages/ automated release
 packages] for the locale.

 The major release is out, so far so good.

 However, when a minor release is out, the localized build still contains
 the old version number (e.g. 4.5 instead of 4.5.2), which is inconsistent
 with English packages.

 Since one of the main points of translate.wordpress.org is to minimize the
 need for translators to deal with SVN, I think Rosetta scripts should
 replace the version specified in the `readme.html` file with the actual
 version number when building the package.

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1696>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org