First, exactly what scribu said.

Second, given the exact nature of the security issue this release fixes, and
the mention that end-users will blindly upgrade without considering that
they may break plugins, themes, etc - this update is even more necessary, as
it could allow lower level users to run updates (or perform more malevolent
actions). If this was not patched, then as 3.1 was released, an author on a
blog could update from 3.0.x to 3.1, and break something. I'd rather the
list of people able to 'break' the installation be as short as possible
(just admins) rather than including all author level users.
___________________________________

Jason LeVan

Email: [email protected]

Twitter: @codeclarified



On Thu, Dec 2, 2010 at 2:05 PM, scribu <[email protected]> wrote:

> This was a security update, so it had to be released as soon as possible.
>
> Also, point releases such as 3.0.1 and 3.0.2 do not bring major changes, so
> all themes and plugins should work just fine.
> _______________________________________________
> wp-testers mailing list
> [email protected]
> http://lists.automattic.com/mailman/listinfo/wp-testers
>
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers

Reply via email to