What is required before we can have a stable release that can recieve support from the drupal security team?

I will go through the issue queue soon and check it out.

Comments

gisle’s picture

Hi,
I just signed on as co-maintainer, and I've started the news job by trying to get to grips with the issue queue.

You can help by going through the issue queue and:

  • Close obsolete tickets.
  • Answer outstanding support requests.
  • Test and comment on patches ready for review.
  • Supply patches for outstanding bugs.

I've also started reviewing and applying pending patches. As of May 3rd, there is a new dev snapshot that contain all the patches from the issue queue that I am confident about.

I expect to put up a RC for 7.x-1.0 as soon as all bugs have been cleared from the issue queue.

Any help towards getting this module ready for a stable D7 release will be appreciated.

gisle’s picture

Version: 7.x-1.x-dev » 7.x-1.0-rc1
Status: Active » Needs review

The 7.x-1.0-rc1 is now available on the project page.

Please give this release candidate a thorough review. Report any bugs you find to the issue queue.

If you take time testing, and do not find any problems, please also report that. We need to have this reviewed and tested by the community before we can move on to a full release.

gisle’s picture

Version: 7.x-1.0-rc1 » 7.x-1.0
Assigned: Unassigned » gisle
Status: Needs review » Fixed

There are no bugs in the issue queue and there has been no bug reports since May 18.
I've just made a full release of the Drupal 7 port of Custom Error.

Status: Fixed » Closed (fixed)

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