delay() can now accept a future date at which run the job

[ItalyPaleAle]

It's now possible to pass a Date object to delay() with a future date in time instead of a number of ms.

[yocontra]

Yess I've wanted this for so long. What needs to get done to merge this?

[behrad]

I've not had enough time to make 0.9.0 release ready... will look into this ASAP @contra
actually I was planned it for the Feb. 28th https://github.com/LearnBoost/kue/milestones

[yocontra]

@behrad Any reason you can't merge things into a new 0.9.0 branch as they become completed, then publish when ready? It would allow people to test out the new 0.9.0 features and provide feedback before the release

[ItalyPaleAle]

:+1 +1 for this change in the way to operate. Eventually, it's common for the master branch to be more "cutting edge" (and tags exist for this reason!)

Right now, my project is configured with NPM pointing at my own fork. As you can imagine, it's not ideal

[yocontra]

@EgoAleSum Right now my project is configured to your fork too 😄

[behrad]

Sorry guys for the delay...

[ItalyPaleAle]

Thank you! Can you also please merge either #500 or #334 ? In particular, #334 has been there for 9 months! (the two patches are very similar)

[behrad]

sure, I will merge that feature in a day or two :)

[ItalyPaleAle]

@behrad sorry to bother you... Any news about merging the other patches?

[behrad]

I'll try to merge some this Thursday @EgoAleSum

[ItalyPaleAle]

@behrad we're all here hanging off your words :)

[behrad]

This is very embarrassing I know, gonna close this today.