Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Request for stable release (=version 1.0) #709
First of all, thanks for this great library! I think this library is the best in it's category :)
Unfortunately, it's a bit pity there is no stable (1.0) version released of this library. For me it's a bit frustrating as I expected a stable a few years ago. While there is some development now after years, I'm afraid there won't be a stable release ever.
I understand if you're busy with other things in live and sometimes things won't go as planned. But thinking out-of-the-box, I think the open issues for 1.0 is to huge.
Also the breaking changes are a bit disturbing, as libraries build on this library has a hard time to get stable. (for example the excellent library HtmlSanitizer - see issues)
So I have a proposal:
PS: I apologize if I sound blunt. Direct language is very common in my home country
The reason for 0.10 is to get feedback for the API and have a stable 1.0. And yes, of course semver is used for 1.0 onwards (I think this is even described in one of the docs).
However, most bullet points still assume that some development is done. The truth is as simple as bitter: The .NET ecosystem and its community did not keep my motivation for development in this space. I still want to conclude the work on this one (i.e., at least leave a 1.0 version behind where only some hotfixes / improvements should be merged in from time-to-time), but time is an issue.
Nevertheless, even though I cannot promise anything I still have AngleSharp on the radar and I'll try to deliver hopefully more soon-ish than late / never-ish. Contributions in any space are welcome. One of the greatest killers was Microsoft's ever growing change. Once we had the nice multi-platform build using dotnet with project.json established the system was outdated. Then NuGet went on to abandon multi-platform support and it became hard to make the system build again on AppVeyor. Hence I believe that a 0.10 will drop most of the multi-platform to only go with .NET Standard (that is of course implied multi-platform, however, not containing all earlier supported platforms).
Regarding 0.11 - I inserted this one for some modifications prior to 1.0 that still should validated before going semver and having to release 2.0 instantly.
TL;DR: The proposal is of course nice and goes in line with my thoughts, however, zero progress is still zero progress no matter how much the scope is reduced.
HTH and thanks for your support!
Thanks for the fast response!
I fully understand your situation and therefore I try to get a stable, with the minimal effort needed.
Luckily I think it's stable now :) Maybe not fully mature, but stable.
I don't wanna repeat myself, but there are barely issues in the milestones 0.10, 0.11 and 1.0 that should block a stable release.