[wp-hackers] Not willing to summon the ancient troll, but... PHP5 in WP 3.0 ?

[Steven Rossi]

Part of me likes the idea, but I'm not totally on board just yet. I really
appreciate the simplicity of the Wordpress install/upgrade process (the
upgrade process having just recently joined in on the simplicity train with
the advent of automatic upgrade functionality), and I would hate to dilute
it too much. I'm not saying that this is a bad idea, but I'd have to see a
more complete picture of how the process would work for less technical
users.

Steven Rossi
http://www.letsmovetothemoon.com
http://www.stevenjrossi.com
http://www.twitter.com/supermoonman

On Wed, Nov 18, 2009 at 12:24 PM, Dan Gayle <dangayle at gmail.com> wrote:

> Please, let at least this happen. I HATE HATE HATE having to always
> upgrade to a new version because the new 'features' introduced in the
> last update included security bugs, etc. How fast has WP cycled
> through it's 2.8.* branch because of bugs, etc.?
>
> I often don't _want_ to upgrade to get new features, since that can
> break custom coded plugins, but we're forced to because there is only
> one branch that also includes bug fixes.
>
> At least two branches, please. Do it like linux or something, with a
> hardened, stabilized release with long term security support, and a
> latest release with the coolest whiz-bang ajax features.
>
> On Mon, Nov 16, 2009 at 2:13 PM, Ken Newman <Ken at adcstudio.com> wrote:
> > Going forward,
> > and for a limited time, there would be support for 2.9.1, or 2.10 etc for
> > security updates, and those users would have to eventually upgrade before
> > support ended. Maintaining two branches (one only for security), but for
> a
> > relatively short term wouldn't be too onerous would it?
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>