[wp-hackers] Grab a seat. On Delaying 2.2, separating tables
peter.westwood at ftwr.co.uk
Mon Apr 16 08:31:09 GMT 2007
On Mon, April 16, 2007 9:07 am, Matt Mullenweg wrote:
> Andy Skelton wrote:
>> Matt, I have not seen your statements on this matter sway a single
>> person. The other committing devs have come out against releasing with
>> tags on the 2.2 milestone date.
> That's disappointing, I thought the discussion on the terms thread was
> generating some ideas better than the existing implementation or the
> "separate tags table." Also read through #3723.
There are a lot of non tag releated changes that have gone in to 2.2
already. There must be other things that we can pull out for the release
announcement that make it worth people upgrading:
# Updated Blogger importer
# WordPress xmlrpc api
# Mail sending improvements using phpmailer
# class-pop3 update
# Performance Improvements.
# Bug fixes, lots of.
> Most importantly, there's movement around an issue that sat around
> The comments from people using the current implementation have been
> good, so I think we have the user side of things down and I'm
> comfortable shipping with that. I think if we get the backend down in a
> way that doesn't compromise terms or performance we have a neat little
> feature done.
Just because we have an acceptable user interface for interacting with
tags does not mean they are ready for release.
The level of discussion around the schema used for storing these
relationships shows how unhappy people are with the current
As stated elsewhere, in this thread, we can never provide a complete API
for plugin authors and as such they will end up interacting with the db.
Therefore we need to be happy with the db schema before we release -
otherwise we have the potential to annoy a lot of people - and break any
number of plugins in the future when we rework the schema.
We need to get the groundwork done for the schema that everyone is happy
with before tags are released.
Tweaking it later is fine.
Peter Westwood <peter.westwood at ftwr.co.uk>
More information about the wp-hackers