Here's the list of remaining issues that need to be resolved before the 5.x-2.5 release:
#219680: Inadvertent dislosure of email address via signup
#243035: How to list all signed up users in a view??
#247573: Hide form for admins to signup users on closed events
#290734: Cleanup, unify and fix hard-coded signup email tokens
Even though the following should be done before the D6 porting, I think it will be better to push these off to a 5.x-2.6 release, but we'll see:
#86462: add backend support for cck date fields
#29568: Flexible number and type of fields
#273072: signup_node_admin_page() needs a theme function
#290305: Split out email functionality into separate submodule(s)
#209954: Allow other modules to alter signup data before it's displayed
#45419: using signup to track who can not attend, maybes, etc
#55168: tracking actual attendance
Comments
Comment #1
dww#137609: Theme function for signup_build_signup_data is now a blocker for 5.x-2.5 (since there are a few bugs that would solve).
#132142: Add setting to use site-wide date formatting strings instead of our own weird setting would be good, just since it's a minor bug that's been around so long and would be easy to fix. ;)
#295542: Add user tokens to those able to be substituted in Signup emails would be nice if we can resolve the problems, but not a blocker (especially since it's a new feature).
Comment #2
dwwOk, this no longer officially blocked. ;)
a) If anyone can test the latest HEAD (or the 5.x-2.x-dev tarball -- just make sure it includes signup.settings.js and you'll know you've got the latest code), and see if they find anything funky, please do. If you find a bug, feel free to open an issue for it. Either way, please report back here.
b) The only issues I'm even considering before the 5.x-2.5 release at this point are:
#295542: Add user tokens to those able to be substituted in Signup emails
#47913-6: More themeability
#86462: add backend support for cck date fields
I'd love feedback from anyone who cares on if we should just ship now and target all three of those for 5.x-2.6, or if we should hold up 5.x-2.5 any longer. I'm strongly leaning towards shipping 5.x-2.5 now and putting those off, but I'm open to discuss it. ;)
Kind souls who wish to test DRUPAL-5 for the 5.x-1.1 release are welcome, too...
Thanks!
-Derek
Comment #3
dwwAfter more thought and work, the only issues holding up 5.x-2.5 are:
#320845: Page / Block option is a little unclear
#321463: "Please login or register" printed even if all auth users don't have signup perms
Both have patches that could use a little more review.
I'm definitely going to wait for the CCK patch (#86462: add backend support for cck date fields) until 5.x-2.6. In fact, that might be about the only issue that 5.x-2.6 is for. ;)
Comment #4
dwwAlso #321980: List all the new theme functions for 5.x-2.5 release. ;)
Comment #5
shanefjordan CreditAttribution: shanefjordan commentedI've been testing the 2.x-dev version and everything looks to be working fine. How close are we to the release for 5.x-2.5? I need to make a switch on our website and would like to run the new release and then move towards the 2.6 version with the cck date support (even though i'll probably run 2.5 with the current cck date patch thats available).
Comment #6
dwwRe: "How close are we to the release for 5.x-2.5?"
Extremely. We just need deviantintegral to take a final look at #320845: Page / Block option is a little unclear (which is probably RTBC). Once he agrees, I'll commit that, then tag/release. Entirely possible that'll all happen later tonight (I only have a few minutes right now, and deviantintegral is in the middle of other stuff, too).
Everything else is going into 5.x-2.6 or later.
Comment #7
dwwRe: "How close are we to the release for 5.x-2.5?"
Extremely. We just need deviantintegral to take a final look at #320845: Page / Block option is a little unclear (which is probably RTBC). I wouldn't mind a 2nd opinion on #322528: Change description of signup_available_signups view, too, but that's not as important. Once those are RTBC, I'll commit, then tag/release. Entirely possible that'll all happen later tonight (I only have a few minutes right now, and deviantintegral is in the middle of other stuff, too).
Everything else is going into 5.x-2.6 or later.
Comment #8
dwwOk, everything I was planning to get done for this has been completed.
I just did some more testing and discovered #132142-11: Add setting to use site-wide date formatting strings instead of our own weird setting and fixed it with http://drupal.org/cvs?commit=147140
Any other testing would be welcome!
Thanks,
-Derek
Comment #9
stBorchertSince noone else seems to test this (:-)) I've done some small testing.
Result: no errors or things to improve (in this release) found.
Stefan
Comment #10
dwwhttp://drupal.org/node/324849
Yay! ;)
Comment #11
shanefjordan CreditAttribution: shanefjordan commentedThank you!!!!
Comment #12
Anonymous (not verified) CreditAttribution: Anonymous commentedAutomatically closed -- issue fixed for two weeks with no activity.