Release version of SharpGLTF nuget

[ansvtrannam]

Hello vpenades!

Thank you for your good job.

I'm very interesting in SharpGLTF. I would like to know do you plan to publish a release version of SharpGLTF nuget? (I mean a SharpGLTF.Toolkit.1.0.0 without the alpha suffix)?

Regards.

[vpenades]

Well... to tell the truth, the release/prerelease thing is more a convention than anything else; and currently SharpGLTF is more mature than many libraries around that state they're release, so if your worry is about whether SharpGLTF is ready for production or not, it is.

Another reason because I keep nuget versions in pre-release is because as glTF standard keeps maturing, I am forced to do breaking changes in the API.... so in a way, keeping the nugets in pre-release is a way of saying: "I can break the API between versions without notice"

It is true that I could switch to release versions, but in practice, it would not change much compared to the way packages are released now, other than the naming convention.

[ansvtrannam]

The reason that we would like a release version:

• We know that features in that version are matured enough to be integrated in the product version
• And it will remove this build NuGet Warning NU510: "A stable release of a package should not have a prerelease dependency....

Therefore, changing the semantic versioning of SharpGLTF will help consumer a lot to predict how impact (breaking changes, non-breaking changes...) and maturity (release or prerelease) to integrate new version of SharpGLTF in product.

[vpenades]

Publishing a release is just a matter of changing the naming convention of the semver, but I need some time to review everything and be sure everything's fine.

There will be a release nuget at some point, but I can't really tell when it will happen.

[ansvtrannam]

I'm looking forward to the release version then. Thanks a lot.

[mzh3511]

@vpenades
I noticed that there are large changes after the alpha0030, do you plan to publish a new alpha version?

[vpenades]

not yet, I'm awaiting for some contributors PR changes to be completed and merged.

[mzh3511]

Thank you for your reply

[gregmarr]

That's good to hear. We are eagerly awaiting the release using System.Text.Json v8!

[pixtur]

I'm really looking forward to an updated release, too.

[vpenades]

Still polishing the Tiles3D extension.

Hopefully, we'll be able to publish new packages sometime next week.

[ilCosmico]

Hello @vpenades,

A release version would solve a problem with non-SDK projects as reported here.

I hope you reconsider the option to publish it, thanks.

[vpenades]

Last release left me exhausted, I didn't even have time to author a proper release tag, so I'm taking a small break.

The plan has always been to release a full version, what I don't want is to release a 1.0.0 version to immediately release a 1.0.1 version 5 days later. This last release has been huge, so I'm waiting for small issues to pile up, fix them, and finally release a full version.

But I don't know when that will happen, I'm full hands at work.

[ilCosmico]

I understand and firstly I want to thank you for the great work.

Anyway, in active library development, releasing multiple versions is a norm to fix bugs or enhance features. Publishing version 1.0.0 is an important milestone, not an endpoint. It's vital to embrace the inevitability of future updates, like version 1.0.1, as part of continuous improvement. It’s all part of the journey to make the library better 😉

[vpenades]

Version 1.0.0 has been published 👍