[wp-hackers] MySQL Version Bump

[Robin Adrianse]

Why would you put system requirements for versions before 2.0? The oldest
non-trunk branch being supported and sub-actively developed is 2.0 -- 1.5 is
long gone and won't be maintained whatsoever...

On 1/11/07, Michael E. Hancock <mhancock at us.net> wrote:
>
> From: "Ryan Boren" <ryan at boren.nu>
> > After much discussion on this list and with various hosts, I think this
> is
> > the plan.  2.0.x will continue to work with 3.23.23 or greater.  2.1will
> > require 4.0 or greater.  2.2 will require 4.1 or greater.  There were
> > several requests for a longer lead time before requiring 4.1.  Delaying
> the
> > bump to 4.1 until the 2.2 time frame should be enough heads up.  Since
> > 2.0.xwill be maintained for a good long while, it is always an option
> > for those
> > who can't or won't upgrade MySQL.
>
> So tentatively, the Codex Server Requirements will read:
>
> WordPress server requirements for versions prior to 2.0:
> * PHP version 4.1 or greater
> * MySQL version 3.23.23 or greater
>
> WordPress server requirements for version 2.0:
> * PHP version 4.2 or greater
> * MySQL version 3.23.23 or greater
> * (Optional) Apache mod_rewrite module (for clean URIs known as
> Permalinks)
>
> WordPress server requirements for version 2.1:
> * PHP version 4.2 or greater
> * MySQL version 4.1 or greater
> * (Optional) Apache mod_rewrite module (for clean URIs known as
> Permalinks)
>
> WordPress server requirements for version 2.2 (not yet released) and
> later:
> * PHP version 4.2 or greater
> * MySQL version 4.2 or greater
> * (Optional) Apache mod_rewrite module (for clean URIs known as
> Permalinks)
>
> Any other adjustments necessary?
>
> MichaelH
>
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>