Opened 9 years ago
Closed 8 years ago
#1696 closed enhancement (worksforme)
Automated release packages should update version number in readme.html
Reported by: | SergeyBiryukov | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | International Sites (Rosetta) | Keywords: | needs-patch close |
Cc: |
Description
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 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.
Change History (3)
Note: See
TracTickets for help on using
tickets.
That only happens if the build uses the SVN branch when no tag was created and the readme wasn't updated.
A few months ago I tried to replace a simple placeholder {{WPVERSION}} in the readmes but that didn't worked well for all files because of different file encodings.