Um. Testing, testing... The irony here is simply painful. :-) I'd say the module is stable enough at this point. Even if there are still issues, that's what later stable releases are for.
Because my workspace didn't have the translations directory when I added the tag and created the release node. Oh well. Can't change it now... what's out is out. I added the tag to the translations dir now, so if someone checks out from CVS they'll get them. Otherwise, they'll just have to wait until 6.x-1.1.
Comments
Comment #1
dwwGood idea. Does everything work? Is this ready? I haven't had a chance to do much testing since the official 6.0 release of core.
Comment #2
hass commentedI haven't tested the module myself yet very much... cannot say, but i thought from past it is stable and you know what you are doing :-)
Comment #3
dwwHeh. ;) Well, if you try it out and report your findings here (or find someone else to do the same), I'll cut a 6.x-1.0 release.
Comment #4
litwol commentedI use the module on my site and i have no complaints regarding it. well just one that its a dev branch and not an official release.
please do an official release soon.
thank you.
Comment #5
hass commentedI think #237347: Table goes hidden on save settings should hold this up.
Comment #6
Crell commentedUm. Testing, testing... The irony here is simply painful. :-) I'd say the module is stable enough at this point. Even if there are still issues, that's what later stable releases are for.
Comment #7
dwwupdate_advanced 6.x-1.0
Comment #8
pasqualleI don't know how could this happen, but the translation files missing from the release
Comment #9
pasqualleComment #10
dwwBecause my workspace didn't have the translations directory when I added the tag and created the release node. Oh well. Can't change it now... what's out is out. I added the tag to the translations dir now, so if someone checks out from CVS they'll get them. Otherwise, they'll just have to wait until 6.x-1.1.