Hi Nate,

The DrupalGardens team is moving over to using 7 betas. So we're trying to get modules we use to also have BETA releases. We'll help maintain the upgrade path when we can of course (we kinda have to) :)

Are you interested in cutting a BETA-1 release of this module?
btw, we also have one tiny outstanding patch #949556: for (var n in ...) not reliable if you feel like committing that it would be awesome (but no big deal if you don't - would still like a release.

Thanks!
Jacob

Comments

quicksketch’s picture

I'm probably not comfortable with beta releases until I start fully supporting Drupal 7. Right now I'm not using this module (or any of my modules) on Drupal 7 as it's not yet a viable platform for development of client sites for us. Labeling the module as beta isn't going to make the module any more stable in itself.

JacobSingh’s picture

Hi Nate,

I agree I guess I misspoke. What I meant was a release known to work w/ DRUPAL 7 BETA 1. We have been using the same tag names just to make it simpler on many of our modules. It's kinda new territory since this is the first time modules are trying to be ready w/ real releases when Drupal releases. Since the upgrade path between beta's is supported, we're trying to the same with modules as much as possible and have a stable point for people to file bugs against.

Is this something you support? Can we help make it happen? You can name is ALPHA-1 or whatever if you want, doesn't really make a difference, just looking for a release. We'll verify each time a core beta release happens to see if the code still works and fix issues as needed.

Best,
J

quicksketch’s picture

Ah, in that case I *think* ALPHA-1 of Options Element works with the latest beta, I'm not 100% sure though. As I said I'm not yet using Drupal 7 so my testing is still pretty minimal on that platform.

quicksketch’s picture

Status: Active » Closed (fixed)

We've now got an official release out and I'm about to make a second one. I think this can be closed.