The editorial flow for 3.6 was the feature that I was most looking forward to in the upcoming 3.6 release, especially with all the editorial work that we do here on WP Daily.
And I know that many of you also shared similar excitement with the coming addition to core as it would significantly increase your productivity and content management.
Alas, it was heartbreaking to hear that it’s been dropped – the justifications are reasonable and I’m not that upset but I may pour out a little liquor for my editorial flow homies.
Mark Jaquith broke the sad news yesterday:
I’ve decided to drop the Editorial Flow feature from the 3.6 roster. A few things happened. We looked into what the main feature (“forking” a published post and allowing it to be edited then reintegrated) would involve, and found that there were some really fundamental hurdles that were unlikely to be resolved in the time given.
A lot of time was spent on the planning stage, and we just kept surfacing more questions. Moreover, because the hurdles were so low-level, they would have required a significant amount of time from a core lead like me,@nacin, or @ryan — time that we just didn’t have to give this cycle due to other responsibilities.
What that left was #12706 — a somewhat related ticket with a long-running monster patch. This similarly needed (and still needs) a core lead to dedicate a lot of time to planning, reviewing, and committing it.
That might happen, or might not. It didn’t seem fair to keep @danielbachhuber and @kovshenin responsible for something that might or might not make it, subject to other people’s availability.
It’s too bad but for it to significantly slow the progress of 3.6 wouldn’t be worth it at this point and is very understandable.
I am encouraged though that they both learned a lot and that they may “tackle” it in the future with more resources and planning. I think that’s legit.
For now, I’m sticking with Edit Flow and the incredible feature set that’s part of our daily activities here at WP Daily.
Join the conversation