Status of the Drupal 6 version of Crumbs

Hi,
I use Crumbs on a D6 production site, and it works.
So far, any time I wanted to have a specific breadcrumb pattern, it was possible to do that with Crumbs configuration, or a little plugin.
I even hacked sections.module, to allow theme switching based on the crumbs trail.

So.. why is this sitting on "unstable"?
I think what this module needs is some more testing and code reviews, and a better documentation of the configuration system.

About the bugs currently sitting in the queue..
"Disabled plugins are still invoked." -> wow, long ago, no idea, need to dive into it again.

The rest is all filed for the 1.x branch, and no longer a problem in 2.x afaik.

-------------

Major feature requests waiting:
#918208: Convert textarea into tabledrag or some other widget
From previous conversations in reallife and in the issue queue, I got the idea that the configuration system is "not for everyone".
Honestly, once you get the logic, it's a fantastic system.
#920510: Support $_GET parameters
Currently, crumbs does look at the Drupal system path, and nothing more. $_GET params are ignored.

I think both of these can be postponed to 3.x.

The other feature requests are nice to have, but we can perfectly live without them. So, postpone to 4.x :)

----------

So, before a stable release, I would like to see
- feedback from testers.
- code reviews.
- I would love to see xdebug benchmarks!

Unfortunately, these things are quite uncommon in the Drupal contrib world.
Maybe i need a co-maintainer for quality assurance?

-----------------------

Should you use the module on a production site?
I think you should give it a try!
But, plan a bit of time for getting used to it, and giving feedback.
Try the latest point release (2.x-unstable-something). Only use the -dev release, if the -unstable does not work for you.

I am happy to explain, if you have difficulties with the configuration.

Crumbs 6.x-2.x has "unstable" releases for quite a while now.
The main reason for it not being in -alpha or -beta or stable is the lack of testing and feedback. If more people would report what is missing, I could make a stable D6 release.

I suggest tagging 6.x-2.0-RC1.
It will probably give confidence to the 100 remaining people that still use Drupal 6 to try the module out, which might lead to additional feedback.

Didn't think much about it, I just find the name confusing :)

I am closing this issue, as Drupal 6 is no longer supported.