make a new release

The one that can create releases, mpotter, is busy as far as I can tell, and whether he deems it worth it to make a new report (making a new release for something that isn't breaking anything -- e.g. just a warning -- seems a bit unusual).

Putting this as a *critical* bug strikes me as totally inappropriate use (abuse) of issue fields.

This is not a bug nor is it critical. Please do not misuse issue status.

edit: My personal policy is not to use critical status unless I'm a maintainer or there's something like data loss happening due to the issue -- misusing it is one way to really step on toes.

edit 2: and thanks fago, task is much more appropriate type. I don't think much early in the morning u.u

A new release would be nice, yep - but it's not a critical bug.

I feel where joachim is coming from but I also agree with hefox that tagging critical is borderline abuse. The error dump is definitely a deterrent for new users.

"borderline abuse" sounds a little harsh, this is just quality control under what is marked a "recommended release". What software have you ever used that throws errors at you when you download a stable version? if its a simple fix why not just spend the five minutes.

Anyways at least everything seems to be working, features is AWSOME for Drupal, I want it to impress people not worry them with unnecessary errors :)

Pretty sure the word "abuse" was used in comments above before some edits happened? I was simply commenting that its borderline at best. w/e

No probs brantwynn I just think that this does harm to drupal's reputation for being stable and supported on such a widley used module.

Anyways I look forward to using a make files etc with stable releases and not getting this error blasting us :)

An RC is not considered a stable version, thus the reason why it's an RC.

Misusing priority and category to gain attention to a issue I defiantly consider abuse; I find it presumptuous and unnecessary. However. discussing proper use of issue status further here is also unnecessary.

I talked to mpotter on IRC and he plans to make that said stable from current dev when he has time.

To my understanding, the decision to make a stable is not influenced but this or the other issue, but by the lack of any truly critical bug reports.

Closing this issue because it is not a productive use of the Issue queue. If you have issues with how a module is being maintained, contact the maintainer or volunteer to help. Hefox has basically said what needs to be said here. If you went into every module that didn't have "stable" (means non-RC, non-Beta, non-Alpha) releases that still had new committed patches not yet rolled into a new release you'd be posting on a LOT of modules. It is NOT something you post a new issue about.

hey all- just here to say the patch worked for me.
thanks for all the great work!