#16033 closed defect (bug) (wontfix)
WordPress 3.0.4 ships with older version of akismet
Reported by: | Ipstenu | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | minor | Version: | |
Component: | Plugins | Keywords: | |
Focuses: | Cc: |
Description
Normally I'd say that we're so close to 3.1 that this is silly, however we've had 3 updates in a short period of time. So ... NOT that I'm saying we need to make 3.0.5, or push it, but can we just bag and tag a placeholder 3.0.5 with the latest and greatest akismet so that IF it has to be used, it's got the right plugin?
http://wordpress.org/support/topic/included-akismet-version-not-current-on-upgrade
Change History (3)
Note: See
TracTickets for help on using
tickets.
This was a known issue with other point releases as well.
We want to keep security releases as small as possible. Additionally, we never want string changes in a minor version.
We will hopefully unbundle for 3.2. In the meantime 3.0.x will be 2.4.0 frozen and 3.1.x will be 2.5.1 frozen.
If there are no string changes in 2.5.2 then we can re-pin it in 3.1.1 assuming 2.5.2 is out by then and that 3.1.1 is a non-security mainenance release. Joseph will need to let us know.