[wp-hackers] fixes for old versions

Glenn Ansley glenn at glennansley.com
Thu Jan 7 00:31:36 UTC 2010


The closest solution may be to identify the security patches in trac and
just applying those to your site.
If you don't know what you're doing though, this may cause you more
headaches than upgrading minor versions.

On Wed, Jan 6, 2010 at 7:06 PM, scribu <scribu at gmail.com> wrote:

> If there was a security problem that targeted WP 2.9 specifically, I think
> it would be fixed. Otherwise, no.
>
> The ideea of maintaining older branches has been suggested several times
> before and has been rejected.
>
>
> On Thu, Jan 7, 2010 at 12:59 AM, Steve Taylor <steve at sltaylor.co.uk>
> wrote:
>
> > A client is worried about the time needed to fully test their site
> > every time there's an upgrade. It is quite a complex system, a custom
> > theme interacting with a bunch of plugins, but it's constructed pretty
> > solidly. Obviously I'll upgrade on a staging server first, but I think
> > only basic tests would be necessary, certainly for point releases.
> >
> > I can't find any information on this, but out of curiosity, is it
> > possible to get *just* security fixes for old WP version? So, say when
> > 3.0 comes out and it jumps up from 2.9.4, would there be a "2.9.5" for
> > the security fixes? My guess is no, but I thought I'd check.
> >
> > thanks,
> >
> > Steve
> > _______________________________________________
> > wp-hackers mailing list
> > wp-hackers at lists.automattic.com
> > http://lists.automattic.com/mailman/listinfo/wp-hackers
> >
>
>
>
> --
> http://scribu.net
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>


More information about the wp-hackers mailing list