nulltoken

@ThisIsMissEm Closing due to inactivity. Feel free to message back would you want to discuss this further.

@P0lip Would #1037 be considered as a relevant contestant? I could work out a repro case if needed.

@brendarearden Thanks for getting back to me. Here's the sample app. Just `npm ci` it and you should be good to go The issue will appear if you open the...

I think we've reached a point where no major blocking features are missing. So stabilization would actually make sense. I'm also worried a bit by potential changes at the libgit2...

I've gone through the opened issues and some of them have now been labelled `stabilization`. Some may make sense, some are more subject to debate (either should be closed or...

@linkdotnet Although not 100% ready, I'd be a taker for a first pass of review please. - `JobRegistrator` now holds the proposed V5 interface for registering jobs. The idea is...

> @nulltoken Good job! > > I am fine as long as this version still works: > > ```cs > public NCronJobOptionBuilder AddJob( > Delegate jobDelegate, > string cronExpression, >...

@linkdotnet I've dropped the deprecations in AddNCronJob() extension and NCronJobBuilder.AddJob(). I'll work on updating the doco in the following days.

@linkdotnet Can we at least deprecate ``` AddJob( Delegate jobDelegate, string cronExpression, TimeZoneInfo? timeZoneInfo = null, string? jobName = null) ``` and only keep the following one? ``` AddJob( Delegate...

> > @linkdotnet Can we at least deprecate > > ``` > > AddJob( > > Delegate jobDelegate, > > string cronExpression, > > TimeZoneInfo? timeZoneInfo = null, > >...