[wp-hackers] Version 3.0

[Andrew Nacin]

The two big things to keep an eye on:

- For better custom post type support, page-new.php, edit-pages.php,
edit-page-form.php, etc., were merged into post-new.php,
edit.php?post_type=page, and edit-form-advanced.php (respectively). That
came with a huge number of backend changes on those panels. Any plugins that
depended on low-level tie-ins here will see some issues. See
http://core.trac.wordpress.org/ticket/9674.

- The number one goal of the MU merge is backwards compatibility, but
keeping an eye on http://core.trac.wordpress.org/ticket/11644 will be a good
idea.

After that, the big things for 3.0 are new features: menu management UI, the
2010 theme, and core plugins.

On Mon, Feb 1, 2010 at 10:22 AM, Brian Layman <bulk at thecodecave.com> wrote:

> >Can anyone give me a webpage or similar that let's me know what 3.0 is
> likely to break and change so I can prepare my plugin for it?
>
> Well, 3.0 is a merging of two different products and core plugin code being
> added . So, anything is fair game for bugs and unexpected consequences.
> However,  your best bet is to download a nightly build periodically to see
> how your plugin works with it. Unless your plugin is gonna be used by
> people
> likely to run trunk, I would wait for about two more weeks before worrying
> about fixing up your plugin.
>
> The schedule shows Feature Freeze on Feb 15:
>
> http://wpdevel.wordpress.com/2010/01/14/per-recent-development-chats-weve-wo
> r/<http://wpdevel.wordpress.com/2010/01/14/per-recent-development-chats-weve-wo%0Ar/>After that it is just bug fixes and then ppl will NEED to know if your
> plugin doesn't work so that WP can be fixed if need be.
>
> Brian Layman
>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers
>