Roll new 7.x release

I'd say that we should go ahead with beta1 because all the submodules have been ported to D7, and a lot of bugs were found and fixed for these ports.

I spent a few hours in the issue queue today and I would like your opinion on #1274026: Page Title lower case in Nodequeue edit form. After that, we're all good for the release :)

Released 7.x-2.0-beta1 and 6.x-2.11 with an impressive changelog \:D/

I'm getting errors from drush, is this just me?

File nodequeue-7.x-2.x-dev.tar.gz is corrupt (wrong md5 checksum).                                                                                      [error]
Updating project nodequeue failed. Attempting to roll back to previously installed version.                                                             [error]

There's an issue with d.o's packaging system: #1286018: Newly generated packages are not available

After more than two years in beta, it seems time for a new version. A beta2 or RC maybe? Is there a list of issues blocking a production release, that I can test?

@Pixelstyle - ditto. 40,000 users should probably make it worthwhile. If you open a new issue I'll meet you there.

Or just reopen this one...

+1 for this, there have been a significant amount of changes in the space of 2 years including this, #1425326: PHP Fatal error: Call to undefined function apachesolr_mark_node() in nodequeue.module line 1084.

With movement on 7.x-2.0 underway it would be good to start tagging release blockers. @fizk seems to be leading the charge so I'll wait for guidance from him.

This is the last active major/critical bug on 7.x-2.x branch:

Issue #205992: allow nodequeues to clear page cache when they get updated (Needs review)

@othermachines Thanks, I'll tag some release blockers. I don't see many right now, but let me know if anything seems important to you.

@othermachines I think we've cleared all the release blockers :) If you see any reason why we shouldn't release right now, let me know.

@fizk Wow, that's great. It's sure been a long time coming! I'm confident if you are but I don't mind having a quick look through the queue this evening.

@fizk - Spent a couple of hours here and there's only the one issue that I'm hesitating on. Unless you think Issue #205992: allow nodequeues to clear page cache when they get updated should be reopened (see my comment) then I think we're good to go. Nice work!

I need to give back to the client a new project and I would love to avoid a dev in my make.

@othermachines - Would be possible to have a release, postponing the #205992: allow nodequeues to clear page cache when they get updated?

Great work everyone, it's a huge release containing tons of bug fixes!

@EmanueleQuinto Thanks for the reminder, I've just released 7.x-2.0.

Awesome. :-)