Module issue queue cleanup [#2148735]

Original post by easycombvba:

Hi,

Is it possible for the maintainer to do a cleanup of the pending patches/issue queue?
If the maintainer is no longer active can we assign a new one to update the module?

Thanks.

Response from dags (co-maintainer):

I would love to get this issue queue cleaned up and to get a stable 1.0 release out there and I think the two go hand-in-hand. It's just quite a time commitment. It'd be great to get another maintainer involved. But cleaning up the issue queue doesn't necessarily require a maintainer -- the community could be of great assistance there. If you have some spare time and would like to help, here are some tasks that could be done:

Close out 6.x branch issues -- Since this branch is no longer maintained, support & feature requests and other "won't fix" could be closed out. Sorry 6.x users. The alternative is to find a 6.x maintainer.
Review 7.x patches and mark them RTBC -- Reviewing patches can be very time consuming. But if patches are reviewed and marked RTBC, a maintainer just has to do a quick code review and bam!.. committed. This would help out tremendously. Look for issues marked "Needs Review."

Comments

Comment #1

dags CreditAttribution: dags commented 10 December 2013 at 20:37

Title:	Module issue que cleanup	» Module issue queue cleanup
Issue summary:	View changes

Comment #2

dags CreditAttribution: dags commented 10 December 2013 at 20:38

Issue summary:

View changes

Comment #3

mengi CreditAttribution: mengi commented 13 March 2014 at 20:58

Is there a current maintainer for 6.x?

I can go and close out the support/feature requests for 6.x en masse if wanted. Currently there are 4 pages of open 6.x issues so this would be a lot of issues closed at once.

What would be the preferred status to update these issues? I believe 'Closed (won't fix)' is the correct one, right? I am also assuming that maintainers would want to leave the 6.x bug reports open.

Comment #4

dags CreditAttribution: dags commented 14 March 2014 at 21:49

No, there is no current maintainer for 6.x.

Yes, 'Closed (won't fix)' is correct and I think leaving the bug reports open would be a good idea.

Closing out those 6.x requests would certainly be helpful for cleaning up the queue and focusing in on 7.x and whatever help you can provide would be greatly appreciated.