Plans for D7 stable release

Hello, we use this module in our distribution, and we need a proper release for it to be packed by drupal.org scripts.

Can we have a new version for this module in order to make this possible? I'm not using alpha 2 due to the bugs in this release being fixed in dev.

Has this project been abandoned?

I've updated two related issues:

#1435242: Make the latest dev release downloadable
#1279328: Recommended Development Snapshot

It would be nice to have a stable release to provide site builders more certainty that the module will get an SA for any security issues. Please feel free to update this issue summary to include links to issues to fix prior to that release.

As of this post, there are no critical bugs in the queue.

You can use the tag D7 stable release blocker to help others identify issues that are blocking a stable release. Currently there are zero issues with that tag.

Agreed, this module is listed as a requirement for Feeds, a wonderful and popular module. Having to install dev or alpha then explaining why I have dev and alpha code on a production system is a problem I'd like to not have.

I can help test if there are stable release blocker issues that just need testers to reach RTBC status.

There's a few little things it would be nice to tidy up (eg #2104533: Unnecessary logs are created) but no major issues in the queue at the moment -- I just closed the only one as it seems to already be fixed.

To my surprise, it turns out I have maintainer access for this, so I could actually make a release... but it's more polite I think to contact the current active maintainer and see what his plans are. I'll send a tweet :)

I think we should definitely do a stable release. I would like to get some of these minor things in before, since this module doesn't get a lot of attention, but let's time box it. A stable release by Monday?

Timebox up :D

128,782 sites currently report using this module, no commits for 18 months.

Surely a stable release can be made?

I think this module needs to be marked as abandoned, unless someone want to be the new maintainer...? There's no mention of why it's listed as not covered by Drupal's security advisory policy, either.

@thomasmurphy I can take it over I'm sure not much else needs to be done.

It's not covered by the security advisory policy as there is no stable release

At the very least, releasing an alpha4 would be very helpful.

@intrafusion let's get you some maintainer status. Here's more information on how. https://www.drupal.org/node/251466. I fully believe this module is unsupported and needs a new maintainer. (9 months later)

As per the official guidelines I have opened #2939712: Offering to maintain Job Scheduler but I suppose I will have to wait the two weeks to give the maintainers time to respond, unless anyone else can change the permissions?

wait the two weeks to give the maintainers time to respond, unless anyone else can change the permissions

Other people (e.g. me) *could* change the permissions before 2 weeks.

But the only people who *should* change the permissions before 2 weeks are the maintainers.

Right I have maintainer access now and I was just planning to create a release of the current alpha3 and mark it as stable as it appears to have been running fine for the last few years, etc.

Are there any current issues which anyone deem as release blockers?

Normally, when there is a stable release of a module, it's covered by the security advisory policy. But here it says

This project is not covered by the security advisory policy.

I wonder why it does in this case?

Mainly because I don't have permission under Apply for permission to opt into security advisory coverage, I would be happy to have this module covered by the security advisory policy.

Thanks for replying so fast, and help maintaining the module. The one-time review process does seems fairly demanding ... I hope the module eventually get to be covered for security advisories.