Hey,

Just wondering if it is time for a release? I ran into a fatal error that is fixed in cvs and is in the dev release. However there is no mention of this on the module overview. There is text that mentions that the -dev version has new features and bugfixes. But it was unclear to me if that meant that there would not be bugfix releases.

#324992: node author notification was not ported properly

I'm glad it is fixed, just thinking a release might reduce support questions, etc.

If this isn't where you want a question like this, sorry.

thanks for your work on this module.

CommentFileSizeAuthor
#1 pastedGraphic.png12.73 KBgreggles

Comments

greggles’s picture

Title: Time for a new release? » Bugs to Fix before 6.x-1.2
StatusFileSize
new12.73 KB

I'd definitely like to make a new release, but we have a bit of a problem. People have seen 1 user interface already (the simple checkbox). We have a new one in 6.x-1.1 but lots of people complained so I updated it to a slightly different one in 6.x-1.x-dev and there were more complaints. So, that makes three total UIs. I'd like to decide on a final good one before we do a release. More specficially, here are the bugs/features to fix prior to a release:

Critical:
#319830: create a simplified user interface

Should do:
#309467: Improper string handling
#317640: Remove "notify" column from comments table
#229582: Provide admin control over default notification for registered users
#186025: Distinguish between new comments and comment edits
#334735: Remove patching core dependency

Might be worth it:
#348000: stop using the $user->data to store preferences

Any help you can provide testing/reviewing those patches would be great.

greggles’s picture

I made some progress in the past week on this list (especially thanks to aclight). These have to be done in a particular order (I've looked up the order twice now so I figure it's worth documenting).

Critical:
#319830: create a simplified user interface

Requires:
#348000: stop using the $user->data to store preferences

This:
#334735: Remove patching core dependency

Requires:
#186025: Distinguish between new comments and comment edits

Should do:
#229582: Provide admin control over default notification for registered users

Done (at least as much as we should require):
#309467: Improper string handling
#317640: Remove "notify" column from comments table

greggles’s picture

Status: Active » Needs work

And #374574: Illegal choice 0 in notify_type element -An illegal choice has been detected. Please contact the site administrator. but that should be easy.

Also updating the status of this issue to reflect the sub issues.

greggles’s picture

Status: Needs work » Reviewed & tested by the community

I just committed a bunch of code - I think it's nearly ready for a new release. Once the tarball is regenerated in a few hours I'll try to get some folks to help test and then create a 1.2 release.

greggles’s picture

Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.