I checked open issues and didn't find anything relevant, but apologies if I missed it.

Is there a list of blocker issues preventing the D11 compatible 2.1.0 stable release from being published? Perhaps this issue can serve that purpose.

Blocking issues:

#3574984: 2.1.0-rc2 keeps asking to rebuild permissions

Comments

xem8vfdh created an issue. See original summary.

xem8vfdh’s picture

xem8vfdh commented

Is this module being monitored by any maintainers?

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Related issues: +#3558323: Offering to co-maintain Content access
liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Version: 2.1.0-rc1 » 2.1.x-dev
liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented

content_access 2.1.0-rc2 is two weeks old and there do not appear to be any release-blocker issues. It can probably be made a full release.

xem8vfdh’s picture

xem8vfdh commented

Awesome, thanks @Liam morland. I agree :)

lpsolit’s picture

lpsolit commented

Before releasing 2.1.0, please check https://www.drupal.org/project/content_access/issues/3574984

xem8vfdh’s picture

xem8vfdh commented

I think thats worthy of review but not at all a blocker for 2.1.0 stable release which is blocking users from moving to drupal 11

reason being, there are two workarounds: 1. rebuild the permissions, 2. refresh the page and the warning goes away?

steven jones’s picture

steven jones commented
Issue summary: View changes

I've gone and marked #3574984: 2.1.0-rc2 keeps asking to rebuild permissions as critical because actually, it'll become incredibly annoying for most sites using content access I think. As explained in #3574984-8: 2.1.0-rc2 keeps asking to rebuild permissions there's some work to do I think!

liam morland’s picture

liam morland
Primary language English
Location Ontario, CA 🇨🇦
commented
Related issues: +#3574984: 2.1.0-rc2 keeps asking to rebuild permissions
xem8vfdh’s picture

xem8vfdh commented

fair enough. Is that the only blocker you see between now and a stable release?

Thanks for the help!

steven jones’s picture

steven jones commented
Status: Active » Needs review

Let's cut another RC.

xem8vfdh’s picture

xem8vfdh commented

Drupal 10 EOL is December this year. The latest stable release of content_access is limited to Drupal 10.

If its decided to publish a new RC and NOT a stable 2.1.0:

  1. this issue should not be marked as "needs review", it should remain open as "needs work" until a stable release is published.
  2. is the plan to still produce a stable 2.1.0 before the Drupal 10 EOL?

I appreciate everyone's help on this, and any other content_access work. Its a great module that deserves a (stable) place in the modern Drupal landscape.

steven jones’s picture

steven jones commented

2.1.0-rc5 is out!

I've had a look at the release stats and plenty of people are using these release candidates, so yeah, I think we're good to declare one of them stable now.

I'll set a reminder for a week, and if we've not heard of any show-stopping bugs, then I'll re-tag 2.1.0-rc5 as 2.1.0 and release.

I think "needs review" is fine, as basically we want people to review the 2.1.0-rc5 release.

xem8vfdh’s picture

xem8vfdh commented

THANK YOU!

steven jones’s picture

steven jones commented
Status: Needs review » Fixed

Done: https://www.drupal.org/project/content_access/releases/2.1.0

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

xem8vfdh’s picture

xem8vfdh commented

awesome, thanks, and congrats on the new release :)

Status: Fixed » Closed (fixed)

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