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.http://drupal.org/project/issues/metatags?version=7.x only shows a few issues, none of them critical.
Are there any blocking issues to creating a 1.0 release of this module? If so, could you tag them as D7 stable release blocker so we could try and get some helping hands on them? This is one of the top 50 projects, and the general lack of porting there is making D7 look scarier than it actually is.
Currently 1 blocking issues in Core: http://drupal.org/project/issues/search?projects=&status[]=Open&issue_ta... (it's in Drupal 8 and is in "needs more info" status?)
Currently 0 listed as critical in this module's queue https://www.drupal.org/project/issues/metatag?text=&status=Open&prioriti...
Currently 0 in this queue that are release blockers https://www.drupal.org/project/issues/search/metatag?text=&assigned=&sub...
Comments
Comment #1
Dave ReidSide note this isn't a port - its a rewrite. Module is still fairly early in the rewrite process, so I'll tag them when appropriate.
Comment #2
Dave ReidHave started tagging issues.
Comment #3
webchickYay! Thanks a lot, Dave!!
Comment #4
Dave ReidHrm, modules sometimes have blockers which are not in its own issue queue, for example, this module currently has a couple pending issues in core and Views:
http://drupal.org/project/issues/search?projects=&status%5B%5D=Open&issu...
How do we best point people to those issues?
Comment #5
webchickOops. Missed this before. I would say track them in this queue, mark as "postponed" and point people over to the real issues elsewhere. This helps reduce duplicate reports since most people will think to search the Metatag project for Metatag bugs as opposed to the Drupal core queue.
Comment #6
webchickOr, maybe just two issues: "Fix the core blockers" and "Fix the Views blocker" or similar.
Comment #7
gregglesLet's use this to help track any other issues.
Comment #7.0
gregglesFixed the link to the issue queue.
Comment #8
DamienMcKennaComment #8.0
DamienMcKennatrack numbers
Comment #9
DamienMcKennaFYI we are getting really close :) One more beta, to fix some somewhat major upgrade bugs, then we'll start building towards rc1 - I'm hopeful for v1.0 really soon.
Comment #10
DamienMcKennaComment #11
DamienMcKennaComment #12
gregglesI updated the counts and made the urls work again (some parameters had stopped working).
I also cleared out the "criticals" queue of this module as it had some non-reproducible issues or feature requests pretending to be critical support issues.
Seems like its basically time for a 1.0! I'll try to get in some QA time on the latest release to confirm its working properly.
Comment #13
DamienMcKenna@greggles: Thanks for the triage work, it's appreciated. There are a few items I've added as subtasks that need to be resolved first, but they shouldn't take long.
Comment #14
DamienMcKennaTo let everyone know, I'm planning to release #Metatag 7.x-1.0-rc2 later this week after completing all of the subtasks, followed by 1.0 a week-ish later if no problems show up.
Comment #15
DamienMcKennaI've just released v7.x-1.0-rc2: https://www.drupal.org/node/2315805
I'm going to give it a few days to work on a reasonable solution for #1391554: Fatal error after switching from Metatags to Metatag, and make sure no other crazy bugs show up, then release 1.0.
Comment #16
DamienMcKennaWe're down to one bug before we can release 1.0, thankfully there's a patch in need of review: #2186155: Metatags corrupted when saving translated entities programmatically
Comment #17
DamienMcKennaI'm pleased to announce that Metatag 1.0 has been released: https://www.drupal.org/node/2340229
Comment #18
DamienMcKennaComment #19
webchickWow! EPIC! Great work, Damien, Dave, et al!