Roadmap to release

I agree, with a set dev release we could at least test that it meets our needs and recommend it to people using it with our modules.

Soon I hope ;) I've discontinued support for Activity 1.x so that I can concentrate on helping Scott more with the Activity 2.x. Next up I'll be trying to get a roadmap for us all so that we can get a tag.

Changing title, turning into task. I'm currently reviewing everything so should be able to have a list of issue to resolve before we do a tag soon.

Ok, after reviewing the issue queue, I think if we get this list taken care of we should tag an alpha.

• #454104: db_rewrite_sql causing errors with DISTINCT - workaround
• #574992: Type Exposed Filter
• #574994: NID exposed filter
• #785700: Activity Delete field handler shouldn't use a confirmation form
• #830800: Node view activity not recorded correctly

Are they critical for an alpha (or even beta) release? I didn't look closely, but it seems only the last one is critical.

I think you're right. If we can get that last one fixed an alpha should be possible.

Shameful subscriber comment.

Quadruply shameful subscriber.

I do not believe number 1 is still happening for most people.

As long as the last one isn't happening then I think we are all good.

The last one has been fixed for a while. Go alpha ;)

...subscribing with interest :-)

Alpha has been tagged and should be available soon.

Not to kick open a closet issue, but this is still on the main module page as the roadmap so I figured it was best to discuss here. I'm happy to move to a new issue if the maintainers prefer that.

There is an alpha release but I'd like to discuss what would need to happen to move to 6.x-2.0-alpha2 or beta1 or rc1 or release. I have been using the module in prod now for close to 2 years. I am manually maintaining the following patches in my local tree beyond 6.x-2.0-alpha1:

#1002952: Regenerate runs into a scalability wall with large node counts, patch from #9 (#23 seems better, but the issue still seems to needs work)
#1172732: Poor index usage with some activity queries, patch from #2
#1186544: Add new hook for activity_delete(), patch from #1

There also seems to have been a fair amount of GSOC commits to -dev from a project over the summer.

My question is this: What do we collectively think should be on the map to fix between now and another release? I'd love to get back on a mainline release branch of code so I can stop maintaining my own patched version. I'm willing to help tie up outstanding issues if need be.

Hey rj,

I'd love your help here actually. Scott and I have both been just not quite interested enough lately to make the time in our busy schedules for this module, so any other helping hands would be appreciated.

Being an advocate for getting patches that are important to you reviewed would be a great start.

Also, taking a look at the current issues and noting here what other patches you think would be important for a release candidate or beta would help.

OK, I'll go through the issue queue and chime back in another subject if anything looks important. No problem, I'll try to do that before the end of the week. I'll also change status where needed (IE, open issues with a patch that are not marked as needs work/review, etc.) I'm going to close some things or propose closing them as well, so if I overstep my bounds here please tell me and I'll stop.

Is this list also representative of the items needed for a stable 7.x release, or has anyone reviewed that yet? Thanks.

hasn't really been reviewed