#5600 closed task (blessed) (fixed)
ReadMe Version Bump To 2.5
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 2.5 | Priority: | lowest |
| Severity: | normal | Version: | 2.5 |
| Component: | General | Keywords: | has-patch tested commit |
| Focuses: | Cc: |
Description
The current readme.html file has the WordPress version hardcoded in. I thought the purpose of wp-includes/version.php was so that we'd only have the version stored in one location.
Attachments (2)
Change History (11)
#2
follow-up:
↓ 5
@
17 years ago
It's not possible to have this grabbed from wp-includes/version.php, because it's a static PHP file that cannot run PHP. This is because the file is designed to be viewed by WordPress users who download the zip/tarball, then look at the readme.html file by double-clicking it in their file browser. Users will likely not read this file as served by a web server -- rather, from a file:// URL, which means no PHP.
That's why it's hardcoded.
#5
in reply to:
↑ 2
@
17 years ago
That's why it's hardcoded.
I realize that it can't be changed to grab the version variable value from wp-includes/version.php, but I don't think that the version number is even necessary in the README, anyway. It creates an extra burden for the developers to bump the version here, too. Also, I don't think it's that important to have in their for the readers in the first place. My patch removes it altogether.
Just added an up-to-date version of the readme file from latest trunk revision.