[wp-hackers] What is the status of adding a new (custom) post status?

[Andrew Nacin]

On Thu, Feb 3, 2011 at 10:31 AM, Bjorn Wijers <burobjorn at gmail.com> wrote:

> Ok, but what can I do to make this happen in the meantime? Do I wait until
> Nacin has some spare time for this? Or can I start on something already and
> lessen his burden ;)


On Thu, Feb 3, 2011 at 11:06 AM, Travis Northcutt <
travis at travisnorthcutt.com> wrote:

> Since there's already a patch submitted, I think it's now just a matter of
> waiting until a member of the core commit team can address it. Regardless,
> I
> don't think it will get released until 3.2 (unless you're running trunk, in
> which case you'll be able to use it sooner, I suppose).
>
> Disclaimer: I may be completely wrong - I'm just trying to help with what
> little knowledge I have. :)


Well, I never have spare time :) but... there was a patch submitted, but it
was really large and had a lot of code churn, and ultimately, the
abstraction and implementation there is going to be very, very subjective.
We need some time to figure out exactly how we want to do it.

Obviously, custom post types have already received that direction. But
there's then comment types, comment statuses, and post statuses (just to
name three things), and we haven't thought through any of those yet. I
imagine you'll probably see comment statuses get some work done in 3.2, and
I do hope to get to post statuses as well, but we'll see. Ultimately, there
needs to be a lot of developer buy-in for it to occur, complete with a full
API that a number of us can get behind.

Once 3.1 is out, we'll be scoping out 3.2 in a project meeting. I would
definitely try to justify why it's needed and what the use cases are, which
can help us decide to back it and also begin to figure out the direction of
the feature.

Cheers,
Nacin