Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The most recent Nodequeue alpha is from May, 2011, and there have been many commits since then. Let's roll a new release :).
@amateescu, what are your thoughts? do you think this should be alpha3 or beta1?
Comments
Comment #1
amateescu CreditAttribution: amateescu commentedI'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 :)
Comment #2
amateescu CreditAttribution: amateescu commentedReleased 7.x-2.0-beta1 and 6.x-2.11 with an impressive changelog \:D/
Comment #3
carn1x CreditAttribution: carn1x commentedI'm getting errors from drush, is this just me?
Comment #4
amateescu CreditAttribution: amateescu commentedThere's an issue with d.o's packaging system: #1286018: Newly generated packages are not available
Comment #6
Dries ArnoldsAfter 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?
Comment #7
othermachines CreditAttribution: othermachines commented@Pixelstyle - ditto. 40,000 users should probably make it worthwhile. If you open a new issue I'll meet you there.
Comment #8
Dries ArnoldsOr just reopen this one...
Comment #9
heylookalive CreditAttribution: heylookalive commented+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.
Comment #10
othermachines CreditAttribution: othermachines commentedWith 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.
Comment #11
othermachines CreditAttribution: othermachines commentedThis 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)
Comment #12
fizk CreditAttribution: fizk commented@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.
Comment #13
fizk CreditAttribution: fizk commented@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.
Comment #14
othermachines CreditAttribution: othermachines commented@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.
Comment #15
othermachines CreditAttribution: othermachines commented@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!
Comment #16
EmanueleQuinto CreditAttribution: EmanueleQuinto commentedI need to give back to the client a new project and I would love to avoid a
dev
in mymake
.@othermachines - Would be possible to have a release, postponing the #205992: allow nodequeues to clear page cache when they get updated?
Comment #17
fizk CreditAttribution: fizk commentedGreat 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.
Comment #18
othermachines CreditAttribution: othermachines commentedAwesome. :-)