[wp-hackers] Dropping the Ball

[Robin Adrianse]

What would be done to support them? Keeping the _categories and _post2cat
and other tables and populating them as well would be a major hindrance, and
regular expressions on DB queries would just be a royal PITA.

Reality is, things have to change sometime, and I for one think the
WordPress development team did a fine job, both in keeping the old function
API and especially in attempting to give due notice to plugin developers and
the like. Extensive lists of compatibility were made on the wiki, numerous
posts were made on the development blog, which shows up in every WordPress
dashboard (unless otherwise removed). I don't know what more could have
done.

So I don't think they "dropped the ball" at all. The WP dev team was
extremely conscious of the incompatibilities that took place and tried to
limit the negative effects that the changes were sure to create.

On 10/18/07, Chris Poteet <cpoteet at siolon.com> wrote:
>
> Team,
>
> WP 2.3 is a monumental step forward for WordPress, and I want to
> congratulate all of you for your hard work.  I'm excited to see the
> future of the application.
>
> The one thing I think that we short-sighted was backwards
> compatibility with the DB schema.  I'm puzzled on why we would
> continue to support legacy/deprecated functions for a time, but we
> didn't do the same for DB tables which lead to almost all of my WP
> sites breaking in one way or another?  Just think in the future we
> could be conscious of this.
>
> Again, great job on the new version, and I look forward to the future.
>
> Chris Poteet
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>