Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

No year field in specification #31

Closed
Jack-Ji opened this issue Oct 26, 2015 · 4 comments
Closed

No year field in specification #31

Jack-Ji opened this issue Oct 26, 2015 · 4 comments

Comments

@Jack-Ji
Copy link

Jack-Ji commented Oct 26, 2015

Wouldn't it be better if we can schedule a job every two or five year?
@Jack-Ji Jack-Ji changed the title Now year field in specification No year field in specification Oct 26, 2015
@robfig
Copy link
Owner

robfig commented Oct 28, 2015

What is the use case for that?

@Jack-Ji
Copy link
Author

Jack-Ji commented Nov 20, 2015

Well, I'm developing an online poker game and trying to use cron package to launch a
Texas Poker Tournament on specific days of specific years, however, the tournament will be lauched
annually without being able to set a year field.

@robfig
Copy link
Owner

robfig commented Mar 28, 2016

Interesting. That's quite a long horizon. I guess it couldn't hurt to support an optional year, if it could be backwards compatible with current specs.

@robfig
Copy link
Owner

robfig commented Aug 9, 2016

This is superseded by #58

@robfig robfig closed this as completed Aug 9, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@robfig @Jack-Ji