[meta] Content Access release 2.0.0

The stable release for Drupal 10 will be 2.0.0.

Cleaned up issue summary.

Added ✨ Restrict Content Type access but show fields in Views Closed: won't fix .

Added 🐛 Does not react to role changes Fixed .

Removed issue added due to a misunderstanding.

Both blocking issues has been resolved. I am creating a release candidate for a full release.

Will appreciate reviews from the community.

Thanks for all of the works @gisle!

I am running 2.0.0-rc1 in production without issue 🎈

So have I. Perhaps it is time for another release candidate with the two changes since the last one.

I am holding back creating another RC until I (or somebody who is bitten by this bug) can find the time to do a proper review of this one: 🐛 Unauthorized users able to view unpublished translations Fixed .

I have closed the last open issue for the 8.x-1.x branch.

The 8.x-1.x branch is reported to have 9632 installs, as opposed to 1641 for the 2.0.x branch. Setting it unsupported is not going to be popular, but doing so may prompt more people to upgrade to the 2.0.x branch, bringing more people onboard for QA and review of that branch. I'll consider it.

If there isn't going to be more development anyway, having it marked as supported could give a false sense of security. It would be better to get a full release.

It would also help to update the automated testing configuration; see 📌 Automated testing configurations Fixed .

thanks for all your work @gisle.

I hear your argument that marking 8.x unsupported might cause some users to shift in their seats, but I agree with @Liam Morland... if you've already decided you aren't supporting the branch, then it's perfectly fine (and appropriate, in fact) to make it as unsupported. Transparency on the current state of the module is good and, as you say, may inspire 8.x users to update and provide needed user experience reports/testing.

As well, moving from 8.x-1.x to 2.0.x means moving from an alpha release to a release candidate. The only major difference is the removal of the rules integration. It's not a total re-write.

We need to have working tests.

awesome! thanks @gisle :)

I think all the issues listed in the issue description are now done :)

@gisle I'll let you review and confirm, and then you can roll the stable release. Thanks for all your work!

This looks great! Steven Jones, thank you for your excellent work!

I'm going to cut a stable release.

I've published a stable version 2.0.0.

wow, congrats/thanks @gisle, this is awesome!

thanks @Steven Jones!

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