[wp-hackers] 2.0 branch

[Simon Wallis]

Well there is clearly is something wrong with the upgrading philosophy. WP
depends in large part on the goodwill of plugin and theme developers. The
upgrade model takes no cognisance of either community. Most commercial devs
need to stick with older versions. They can not afford the stress or the
financial cost of re inventing the wheel every time they do an install.

On 7/28/07, Alex Günsche <ag.ml2007 at zirona.com> wrote:
>
> On Sat, 2007-07-28 at 13:13 +1000, Jeremy Visser wrote:
> > Alex Günsche wrote:
> > > (For example, I use only 2.0.x for myself and for customer projects,
> > > as I couldn't guarantee consistency accross upgrades with the later
> > > series.)
> >
> > In what way? If that were the case, that would suggest something is
> > seriously wrong our upgrading philosophy.
>
> Mostly because of plugins, which may break or malfunction with upgrades.
> But also because of changing core functions used in plugins and themes.
> If I install WordPress for somebody, I do not want to fix broken
> features on every release. I want to have a perspective of some years
> with the least amount of internal changes.
>
> Alex
>
> --
> Alex Günsche, Zirona OpenSource-Consulting
> http://www.zirona.com/ | Hilfe für das HQ AC: http://www.prohq.de
> PubKey for this address: http://www.zirona.com/misc/ag.ml2007.asc
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>