search

quartz-scheduler / quartz

Code for Quartz Scheduler
http://www.quartz-scheduler.org
Apache License 2.0
6.29k stars 1.94k forks source link

Quartz Scheduler is abandoned? #1134

Closed lprimak closed 4 weeks ago

lprimak commented 5 months ago

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 commented 5 months ago

the same inquiry

IOhacker commented 5 months ago

x3

RichardBradley commented 5 months ago

There's some conflicting info from "Software AG" quoted in this thread from April 2023: https://github.com/quartz-scheduler/quartz/issues/839#issuecomment-1479458400

lprimak commented 5 months ago

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

lprimak commented 5 months ago

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

bmertens911 commented 5 months ago

@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 commented 4 months ago

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 commented 4 months ago

@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 commented 4 months ago

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 commented 3 months ago

@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 commented 3 months ago

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 commented 3 months ago

@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 commented 3 months ago

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 commented 3 months ago

@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 commented 3 months ago

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 commented 3 months ago

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 commented 3 months ago

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

lprimak commented 3 months ago

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

gklijs commented 3 months ago

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

lprimak commented 3 months ago

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

jcputney commented 3 months ago

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

melloware commented 1 month ago

Expect an update soon-ish...

linghengqian commented 1 month ago

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.

wilx commented 1 month ago

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

melloware commented 1 month ago

@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 commented 1 month ago

I found this recently: https://github.com/quartz-scheduler/quartz-scheduler.org-site/commit/ca9b8a38757ddd1df5cb18e8f4547525362ba3f6 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 commented 1 month ago

@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 commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

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 commented 1 month ago

I have started a discussion area https://github.com/quartz-scheduler/quartz/discussions/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.

https://github.com/quartz-scheduler/quartz/discussions/1166

melloware commented 4 weeks ago

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

lprimak commented 4 weeks ago

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

bcode2 commented 4 weeks ago

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 commented 4 weeks ago

@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.