It's been over a year since the last stable release. No that there's an agreed to best practice document yet, but we need one #2186377: Highlight projects that follow Best Practices

Please consider putting out a new stable release.

Comments

mpotter’s picture

I'd like to see a 1.4 release just so people can get the Features support.

damienmckenna’s picture

Title: Time for 7.x-1.4 or 7.x-2.0 beta? » [META] Plan for the Workbench Moderation 7.x-1.4 release
Version: 7.x-1.3 » 7.x-1.x-dev

Lets focus this a little bit.

Are there any blockers for the 1.4 release? Those should have this issue listed as the parent, that way we can help focus everyone's efforts.

damienmckenna’s picture

FYI the 2.0 release is being managed separately: #1862580: [META] Plan for Workbench Moderation release 7.x-2.0

colan’s picture

I'm trying to get this sorted out over at #2259083: Offer to help maintain 1.x branch. Going to commit everything to my own repo for now (and possibly stick it on GitLab if I don't hear back soon).

colan’s picture

colan’s picture

Assigned: Unassigned » colan

See #2259083: Offer to help maintain 1.x branch for the plan.

Once everything's in dev, we'll let it bake for a little bit to make sure there are no major problems. Then we can cut a release. If you'd like to help, please keep an eye on that branch, and keep testing it. (I'm still committing RTBCs as we speak.)

colan’s picture

Okay, test away; all of the RTBCs are in. If there are no major problems with the dev branch, I'll cut a release in a couple of weeks.

colan’s picture

Shooting for a February 13th release.

@hass: I'm following those, but neither of them are RTBC at the moment. If this changes by then, it would make sense to include them.

hass’s picture

If something is RTBC in contrib I would fear they are really rtbc. :-) You need to review very careful. The performance issue is open for such a long time and only a maintainer can review this properly I think.

colan’s picture

Status: Active » Fixed

7.x-1.4 has been released, and will be published shortly.

The only critical issue that showed up for me in the two-week window was #1492118: View all unpublished content permission not working, which is included.

The issues mentioned in #8 aren't included; they're not ready. As suggested above, let's get all of this stuff reviewed properly before rushing to include it. It can be included in a future release once ready.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.