Quartz.Net 还在更新吗？如果没有其他选择？
我正在查看 Quartz.Net ，这似乎是大约一年前的事了。
我想知道他们是否停止了开发，或者下一个版本只是需要一段时间才能完成？
我问这个问题是因为我真的不想把时间投入到生命周期即将结束或不再开发的东西上，因为我只知道将来我将不得不升级到不同的东西，所以也可以从别的事情开始吧。
当然，无论我选择什么，将来也可能不会开发，但我希望在我开始使用该产品的几个月内看到新版本。
如果它死了，有人还有其他仍在研究中并且具有与 Quartz 相同功能的替代品吗？
I am looking at Quartz.Net and it seems to be almost a year ago.
I am wondering if they stopped development on it or it the next versions is just taking a while to do?
I am asking this because I really don't like to invest time in something that is at the end of its life or not being developed on anymore because I just know in the future I going to have to upgrade to something different so might as well just start with something else.
Of course whatever I choose might not be developed on in the future either but I like to see new versions to be a few months within the time I start to use that product.
If it is dead anyone have any other alternatives that are being still worked on and have the same features as Quartz?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
Quartz.NET 的开发并没有完全停止，它只是转移到github 。如果您检查 sourceforge 上的源存储库，则最后一次提交是 4 个月前，并且明确表示“源已移至 GitHub，删除了主干，因为目前它具有误导性”。
github 存储库目前有 28 个观察者和 8 个分支，以及活跃的贡献者（即，这不是一个人的表演），因此该项目绝对不会很快消亡。
顺便说一句，最新版本是 1.0.3（2010 年 8 月），在撰写本文时，这比一年前要少得多。
Quartz.NET development hasn't stopped at all, it just moved to github. If you check the source repository at sourceforge, the last commit was 4 months ago and it clearly says "Source moved to GitHub, removing trunk as it's misleading at the moment".
The github repository has currently 28 watchers and 8 forks, and active contributors (i.e. it's not a one-man show) so the project is definitely not going to die any time soon.
By the way, the latest release was 1.0.3 (August 2010), at the time of this writing this is much less than a year ago.
Quartz.net 实际上非常活跃。我已经写信给 @lahma 几次询问错误，他在很短的时间内修复了它。
几个月前我尝试过 2.0，但它有点问题。
我知道有一个新的 API。你也许可以尝试一下。
Quartz.net is actually very active. I've written to @lahma a couple of time for bugs and he fixed it in a very short time.
A couple of months ago I had tried the 2.0 and it was a little bit buggy.
I know there's a new API. You might give it a go.