NCronJob-Dev
[V5] Breaking changes proposals
Although V4 is not done yet, this placeholder is a proposal to hold discussions about things that may need to be changed but would induce a breaking change
I like that. I added a v5 milestone. I am fair with breaking things fast, as long as we have migrations and can guide the user.
If we start working on v5 I would put v4 into maintenance because otherwise, it leads to waste.
@linkdotnet Here's a first batch of things to ponder about. Each of them in a separate sub-issue to be able to focus the exchanges per topic and potentially ditch it easily if deemed irrelevant.
Some additional ones may pop up later :wink:
@falvarez1 feel free to add stuff. Let’s break things as long as the window is open
If we start working on
v5I would putv4into maintenance because otherwise, it leads to waste.
I'd suggest to keep v4 open for now. I believe there are still things that can be tackled without incurring breaking changes.
If we start working on
v5I would putv4into maintenance because otherwise, it leads to waste.I'd suggest to keep v4 open for now. I believe there are still things that can be tackled without incurring breaking changes.
If they are small I am absolutely fine with that. But the more they diverge, the bigger the mess. The library isn't big anyway, where migrations are normally small (from a user's point of view)