Merge "Needs backport to 7.x" term into "Needs backport to D7"

Yes please. It's silly to have two separate tags that mean the same thing, and it translates to having to search for both tags all the time in views of issues on which I try to facilitate work.

I think D7 is a better choice anyway because it is project-agnostic, whereas 7.x implies only core.

I'd also say the same for the backport to 6.x and D6 tags, although these are far more infrequently encountered in practice.

Not sure if there's a way to automate this, but it might be worth the trouble of writing the code to do this so that everyone can agree on what is the actual tag and which similar tags should automatically be renamed to the right one.

Working on this...

There were over 100 of these, but they're taken care of now.

I hope that the term "Needs backport to 7.x" won't popup anymore in the autocomplete, or we can dow this work again in a few weeks time. Quick test: it does popup, and even above the preferred term...

Oops, removing the 'tag' that stayed there after I tested it.

> I hope that the term "Needs backport to 7.x" won't popup anymore in the autocomplete, or we can dow this work again in a few weeks time.

The tag 'Needs backport to 7.x' still shows up in the autocomplete just now.

If it has no more nodes tagged, could it be deleted?

WOW! Thank you for doing that!!!

Finally! Thanks cweagans for all the issue updates that I saw come through email today, and thanks tim.plunkett for deleting the term.

So, should we do the same for the "Needs backport to 6.x" tag (which is still present in the autocomplete)?

FWIW: We badly need a better taxonomy term management interface and capabilities in core. Having to do this manually is ridiculous for a system that claims to be a content management system. I would be more than happy to review and help with patches that improve the situation.

Is there already a D7 module that does this that we could consider adding to d.o after the upgrade?

I agree that term management is badly needed. Too many terms are bad for performance and for usabiliy

Taxonomy Manager is pretty bloaty and not a very Drupal-ish admin UI at all.

Not a problem! Hope it helps :)

@tim.plunkett, thanks for pointing to that :) Way too heavy though. ;)

However, that project description contains a direct link to http://drupal.org/project/term_merge which is way more focused on the actual problem.

Relatively small, but nevertheless, the code looks a bit suspicious to me. Might merely be the coding style though... It is definitely lacking tests. Those issues should be easy to resolve though.

#1681640: Review and install term_merge on Drupal.org filed

So I manually did this again today, for the fifth or sixth time since 2012.