Problem/Motivation

The issue queue is full of issues which are targeted at the 7.x version of this module.

Proposed resolution

Agree a way forward for these issues in order to clean up the issue queue. The way I see it we have two options:

  1. Attempt to recreate the problem on every single issue in the latest version of the module and if still present change the target version of the issue.
  2. Close all 7.x issues as out of date and request the OP to re-open if issue persists in latest version.

Remaining tasks

Discuss best way to begin cleaning up the issue queue so we can focus on the actual issues that are affecting the latest version of this module.

Comments

darren.fisher created an issue. See original summary.

d.fisher’s picture

d.fisher commented

Any thoughts on this?

alison’s picture

alison
she/her
commented

@d.fisher great thought, thanks for this issue and for the nudge.

Potential option 3: Change to "postponed maintainer needs more info" and comment on each one explaining that we're doing housekeeping (maybe link to this issue, #3516593), and if there's no response, we'll close them after, idk, 2 weeks? -- and folks can re-open if they come back to it later.

I think option 2 and this potential option 3 are both practical and fair, all things considered. WDYT?

d.fisher’s picture

d.fisher commented

@alison. I like your option 3. Would you like me to go ahead and do that?

How's this:

---

Drupal 7 security support has ended as of 5 January 2025.

We are doing some housekeeping on the nodeaccess issue queue and moving all Drupal 7 issues to "postponed (maintainer needs more info)". See https://www.drupal.org/project/nodeaccess/issues/3516593.

If this issue persists on the latest dev branch of nodeaccess (2.0.x-dev) then please feel free to comment and we will change the version against this issue. If we do not hear any feedback within 2 weeks (8th October 2025) we will go ahead and close this issue as outdated.

Thank you.

alison’s picture

alison
she/her
commented

Perfection! Thank you!

Do you want to split them up or do you want to do them all? (No pressure either way)

d.fisher’s picture

d.fisher commented
Assigned: Unassigned » d.fisher
d.fisher’s picture

d.fisher commented

I've done them. There were way more than I realised!! I'll leave this issue open until the 9th October 2025 when I will go back through all those that have gone stale (not been replied to) and closed them. This should help us to identify if there are any long standing issues that still aren't fixed and streamline the issue queue into something more manageable, hopefully.

alison’s picture

alison
she/her
commented

Fabulous, thank you!

d.fisher’s picture

d.fisher commented
Assigned: d.fisher » Unassigned
Status: Active » Fixed

I've now closed as outdated all of the Drupal 6 and Drupal 7 issues that have not had any updates or replies. Closing this issue as fixed as that task is now done. Any issues which are found to persist on 2.0.x-dev can be re-opened but at least now we have cleaner issue queue to triage!!

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

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

Maintainers, please credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

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