Are we ready for 7.x-1.0-rc2 or 7.x-1.0 releases?

Or is there a list of release blocker?

Comments

rooby’s picture

rooby CreditAttribution: rooby commented

This would be great, there are some much needed fixes in dev.

rudolfbyker’s picture

rudolfbyker
Primary language Afrikaans
Location South Africa
CreditAttribution: rudolfbyker commented

Agreed. If there are any release blockers, I would like to help with writing patches to solve them. The issue queue is HUGE, so an indication of what to start with would be helpful.

rooby’s picture

rooby CreditAttribution: rooby commented
Priority: Normal » Critical
Issue summary: View changes

If I can also help to get a new release out I can allocate a little bit of time.

I have a project that cannot really use development versions of modules due to security policies but there are a lot of useful fixes in dev and I have had to spend some time working around problems in the latest release that are fixed in dev, and that is time I could spend helping to make a release.

(changing status because I'm an attention seeker :))

rooby’s picture

rooby CreditAttribution: rooby commented

I suggest this is one that needs to be addressed because it is security related: #2126753: Restrict forum landing page and forum category pages

mgifford’s picture

mgifford
he/him
Primary language English
CreditAttribution: mgifford commented

The current stable release was released in 2011-Sep-10. It's definitely time for a RC2 or even a stable 1.0 release.

I've proposed #2186377: Highlight projects that follow Best Practices to address what is a best practice for modules but I'm really not sure what can arbitrarily be evaluated.

Most importantly though, how do we address the call Seeking co-maintainer(s) from the maintainer? There are over 5k sites using the D7 version of this module. This should be large enough to maintain this code better.