Time for a 7.x-2.0 Release or at least a 7.x-2.0-beta2 + Co-Maintainer

It's just not cool to have a module sit at 7.x-2.0-beta1 for nearly two years. Now a beta is still better than only having a -dev release, but nearly 4000 sites are using this module.

Now this might sound harsh on the maintainers, but it's really not intended that way. We really don't have many incentives for people to update modules. We haven't really defined module release best practices. I've proposed #2186377: Highlight projects that follow Best Practices but I'm really not sure what can arbitrarily be evaluated.

The maintainer is clearly seeking help by setting the status as Seeking co-maintainer(s). What can be done to help find a co-maintainer for this module? What incentives to we have to offer? I've suggested these two, but there are many others we could imagine #2138397] & #2177459: Highlight Supporting Organizations in the Issue Queue

We need a 7.x-2.0 & we need a co-maintainer who can put some time into looking after this module.