Is a New Update coming Soon?

Update
I have tracked down the current Developer for this Edit Flow plugin, it is Automattic.
The other developers (contributors) of this plugin are no longer involved.

I have sent a message to Automattic to come to this support forum and settle this matter about the plugin’s life, whether they are going to continue support and development or is it officially dead.

I am hoping they respond.

As a note, it is pretty irresponsible to keep this plugin in the www.ads-software.com repository and support forum open when they no longer want to support it. They should have removed it from www.ads-software.com and closed this forum.

Also a note to others, your issues with the plugin are likely due to the lack of updates and compatibility with WordPress versions that are higher than 5.0.6

If you’re curious about the work that Automattic is doing with Edit Flow, it may be helpful to check their repository on GitHub: https://github.com/Automattic/Edit-Flow

The contact listed there is [email protected] – I’m not sure if that’s monitored anymore, since the https://editflow.org/ website is pretty far out of date.

Automattic uses Edit Flow as part of their WordPress VIP packages, as seen here: https://wpvip.com/plugins/edit-flow/

In 2016, when the plugin hadn’t been updated for a long time but many people were concerned about the status of the plugin, Jeff Chandler at WPTavern published articles that helped get Automattic listed as a co-editor and updates posted to the plugin repository here on www.ads-software.com:

Article 1: https://wptavern.com/hey-automattic-whats-going-on-with-edit-flow
Response: https://wptavern.com/edit-flow-lives-new-update-fixes-bugs-and-improves-performance

In 2017 Sarah Gooding published this article about a forked plugin based on Edit Flow: https://wptavern.com/pressshack-forks-edit-flow-to-create-publishpress-aims-to-improve-multi-user-editorial-workflow-in-wordpress

That plugin continues to be updated (as of today, the last update was 3 weeks ago) and may be an alternative for those dealing with bugs in the current Edit flow version:
https://www.ads-software.com/plugins/publishpress/

Emily Barney (@ebarney):
Thanks for the information. It seems you are involved with this plugin, in someway, to be able to list so many of those type of references.

Although, I would have to disagree with your last paragraph. Edit Flow plugin shows it has not been updated for the past 8 months (7 months at the start of this post string). The changelog for the “Free” version of this plugin shows the last update as January 10, 2018.

Just because Automattic includes this plugin with some VIP package does nothing for the its dead-like status here.

This is the main Support Forum for this free plugin version, not the other links. Many people who use it are no where near developer level and have no interest in it any further than being a user of the plugin. So as much as your links may offer assistance, it is only to a small few.

What Automattic has to do is come here and settle this plugin status issue one way or the other and if they want to keep the “Free” version alive, update it in the current www.ads-software.com plugin repository.

Does that make sense?

==PS:==
GitHub: the Edit Flow plugin there is the same out of date one. Same change log and only tested to WordPress version 5.0.6.

PublishPress:
I looked at the other free plugin you listed “https://www.ads-software.com/plugins/publishpress/”, and I would say that it is not right to send people there thinking they are going to get help for the Edit Flow plugin when that support forum is for the PublishPress plugin.

The place for Edit Flow (free) plugin has been established as here, not there.

(@ebarney)
Thanks for your reply.

Still, someone who can speak for Edit Flow (Automattic) needs to come here and settle this plugin status issue.

Responsibility
The one thing I know is completely irresponsible of plugin developers is to completely ignore a plugin they no longer support, allowing it to continue in www.ads-software.com downloads while it falls into code degradation where it ends up in conflict with WordPress and other related functions.

All plugin developers have a responsibility to their plugins, to provide the support to a plugin they want to keep alive or “close” the plugin completely when they decide to shut down their involvement or when they decide to move it from Free status to Premium status,

…but to Never leave it to rot, while people continue to download it, as it creates nothing but problems for WordPress users, which includes any security issues for their site, is pure irresponsibility.

The responsibility to the plugin sits squarely on the developers shoulders, not the user’s shoulders.