Quartz Scheduler is abandoned?

[lprimak]

Update: Quartz Scheduler was abandoned. - But not any longer.

Can anyone with knowledge shine light on this?
To me, it looks abandoned. No commits this year at all, CVEs not fixed, no issues answered, etc

Thank you

[Yannis-01]

the same inquiry

[IOhacker]

x3

[RichardBradley]

There's some conflicting info from "Software AG" quoted in this thread from April 2023: #839 (comment)

[lprimak]

@RichardBradley Thank you for pointing this out. Looks more and more abandoned to me.

[lprimak]

2 weeks with no response?
I think the conclusion is obvious. Quartz Scheduler is abandoned.

[bmertens911]

@lprimak @RichardBradley @Yannis-01 @IOhacker @Yannis-01 @vmptk @cunhaax - we've switched to https://github.com/jobrunr/jobrunr years ago and could not have been happier. Better performance, new features, an integrated dashboard and if you take a Pro version (which we needed for workflow support), you also get awesome support.

[pbartoszek]

bmertens911 jobrunr looks very nice. However open source free version doesn't seem to support transactional jobs :(. Pro version does support @transactional and costs only $15k per year...

[abccbaandy]

@lprimak @RichardBradley @Yannis-01 @IOhacker @Yannis-01 @vmptk @cunhaax - we've switched to https://github.com/jobrunr/jobrunr years ago and could not have been happier. Better performance, new features, an integrated dashboard and if you take a Pro version (which we needed for workflow support), you also get awesome support.

jobrunr free version is 100% waste of time unless your project is just for fun.
You can just check the PRO version feature in the doc, you will find out many "needed" feature is there.

And the author even add "trap" in the free version.

[lprimak]

Please stay on topic.
The fact that jobrunr folks want to get paid for their work is not applicable to this particular discussion.
This post isn't really meant as a recommendation for other projects or products in the space please.

[melloware]

@lprimak i agree the lack of a release cadence from a corporate backed library is disappointing.

However if you look at the branches there is a 2.4x branch they have been working on that supports Jakarta and has had more recent commits than 5 years ago. But still no release.

This project just needs more volunteers and stewards to watch it.

[lprimak]

There hasn't been a commit to any branches in a year and 3 months.
Sorry, but it's clearly abandoned and I just don't see this being resurrected at all.
Anybody can make a fork I guess, but I just don't see this happening

[melloware]

@lprimak i agree its dissapointing. I have Quartz in a few mission critical applications since 2014.

If you are looking for an alternative this one is Open Source but not as full featured as Quartz: https://github.com/lukas-krecan/ShedLock

[bcode2]

I have been using version 2.4.0-rc2 without any issue almost for a year, but I agree, it seems the project updates goes very slowly.
I just ask myself why those companies that use it do not contribute to the project. (Donations or code updates)

[lprimak]

@melloware I feel your pain. I know this sucks. We have the same issue with Apache Shiro.
However, with security framework, we can't have dependencies where CVEs are not fixed.

Just to make my point clearer for others reading this:

Unfortunately, hoping that Quartz Scheduler will have any updates or releases in the future is just wishful thinking.

According to my (and others) research, maintainers were (are?) employed by Software AG,
who is no longer sponsoring this project. It is clear that all maintainers moved on for over a year.
If there was another company / entity who was interested in hiring the maintainers to work on this,
it would have happened already.
I also don't see the maintainers transferring ownership to anyone else to avoid the "xz" security issue, it's just too much risk.

If this was Apache project (I am Apache PMC member) this would have been long in the Attic.
However, GitHub doesn't have such provisions, so if maintainers don't touch the project, nor will they archive it,
it'll just sit there without any hint of it's "abandonment"

This is why I created this issue in the first place, to hopefully inform people of the facts of where Quartz stands.

All of this is unfortunate, and I don't like it anymore than anyone else, but facts need to be stated.

[melloware]

As a note I volunteered years ago to be a committer and also perform releases for Quartz and they rejected the idea. I know they said they were looking for help but I guess they were not serious about it.

Also the fact that it was purchased by Terracotta and then it looks like purchased by Software AG it seems they don't care. It's not mentioned anywhere on the software AG site.

[melloware]

OK some good news. I know someone who is in contact with Software AG and we may have some progress on this in the near-ish future.

[bcode2]

Excellent!!!!,. If the project goes ahead and there will be someone reviewing and accepting pull requests count on me to do some contributions.

[lprimak]

While I am hopeful that @melloware gets somewhere with this,
I would urge caution until the actual CVEs are fixed.

[gklijs]

https://github.com/kagkarlsson/db-scheduler is another nice alternative..

[lprimak]

And let's not forget that Jakarta EE has robust scheduling features built in.

[jcputney]

It has scheduling features, but I don't know if I would go so far as to call them robust

[melloware]

Expect an update soon-ish...

[linghengqian]

we've switched to https://github.com/jobrunr/jobrunr years ago and could not have been happier. Better performance, new features, an integrated dashboard and if you take a Pro version (which we needed for workflow support), you also get awesome support.

• At least on the ASF project side, it is not possible to use jobrunr/jobrunr. jobrunr/jobrunr uses LGPL-3.0-only, which means that for ASF projects, it can only be used in unit tests and build processes. See https://www.apache.org/legal/resolved.html .

[wilx]

I see that some work towards the Jakarta namespace has been done on main. What is missing for a new release to happen?

[melloware]

@wilx i think there are some steps that need to happen.

1. Release the current 2.4.0 as an official release.
2. Then work on a 2.5.0 release for Jakarta.
3. Review all PR's and create a 3.0 on JDK21 and VirtualThreads.

That is just my two cents.

[dellagustin-sap]

I found this recently: quartz-scheduler/quartz-scheduler.org-site@ca9b8a3
It seems that quartz was transferred to IBM, together with other IPs (see https://newsroom.ibm.com/2024-07-01-IBM-Completes-Acquisition-of-StreamSets-and-webMethods,-Bolstering-its-Automation,-Data-and-AI-Portfolios).

[melloware]

@dellagustin-sap yes IBM has purchased. Glad its official now and I have been in touch with the Quarkus Team (also IBM) and they are working with IBM to get this library maintained!

[jhouserizer]

Yes, IBM has acquired a group of products from Software AG , of which Quartz comes along in the collection. The past years within SAG have led to some legal stalemates around handling contributions and other matters that stifled progress (to be clear, no dispute of existing code IP). Once we have IBM-sanctioned policy/procedures/re-copyrighting, etc. (e.g. for CLA/DCO, etc.) in place we should be able to get Quartz moving again.

I see there are a few here that are eager - that's great.

[jhouserizer]

Questions were answered/clarified. Contribution terms, dco, etc. and PR template was updated.

I have closed all open PRs with the comment "Unfortunately, due to the change of ownership of this project, the terms of contribution have been updated, and this PR will need to be re-created, agreeing to the new terms."

[jhouserizer]

There is a weird situation where currently copyright ownership is set (in file headers etc.) to "Copyright Super iPaaS Integration LLC, an IBM Company 2024", and on January 1st it will need to be changed to "Copyright IBM 2025". Fun!

[jhouserizer]

I have started a discussion area #1166 for those of you anxious to get official 2.4.0 and 2.5.0 releases out - help us identify what needs to be done. My time is still limited and there's a lot of open stuff to wade through - not so easy to quickly identify what matters. Also feel free to indicate volunteering to tackle something.

#1166

[melloware]

@lprimak probably safe to close this ticket as we know its not abandoned anymore

[lprimak]

I think so... I think the release can be made :) which is a real test

[bcode2]

I am not agree there is a bunch of things to migrate and refactoring, I guess with the current speed of PR approved,in a couple of weeks would be fine

[melloware]

@bcode2 i think we are just saying that this project is not abandoned anymore so this ticket isn't valid. That is all we are saying.