What is release strategy of ElectronNET.Core overhaul

[KristinaPlusPlus]

So we are seeing full releases of a v0.1.0 and v0.2.0 along with pre-releases. But based on the version numbers, are these to be treated all as betas? And if these are stable releases, why then was v0.2.0 pulled?

If there are can be just a slightly illumination of the roadmap forward of this overhaul and approximate timeline for a production ready release of this new change, would be helpful. If this is not known, that is fine but just looking for some clarification as the wiki does not provide this.

[softworkz]

For my use case, I wouldn't hesitate on putting it in production, even though our app is moving from small-group beta to public beta only, this week. And for all the preceding small-group months, issues originating from Electron.NET Core bugs were rare (and all fixed).
Albeit, it's also a very specifc use case (Linux only, using just a small set of APIs), so it doesn't necessarily mean to be the same for everyone.

On the other hand, I think it's valid to say that the current state is by a magnitude better than Electron.NET has ever been before. The reason why there's no 1 before the dot, is rather about expecting for unexpected problems - like here: #963 where publishing the project caused deletion of all project files - which can hit one really hard.

When it happened, I was just glad that the version still has a zero in front.

[FlorianRappl]

See #918 (comment) as how to proceed.

In general this is the future of Electron.NET and you can already use it. Yes, you can treat the 0 in front as kind of a beta indicator. The idea is to get a bit more experience with use cases and migration issues before calling it a 1.0 release.