search

CoreWebForms / CoreWebForms

MIT License
87 stars 13 forks source link

NuGet release version #321

Open gumbarros opened 5 months ago

gumbarros commented 5 months ago

For compliance reasons I can't use the custom feed (GitLab CI/CD pipeline at on-premise server without external access), and also my team and customer won't feel comfortable with a pre-release tag. Is there a NuGet feed and Release version in the plans 👀?

Looking so forward to use this and finally remove.NET Framework and VB.NET from our dependencies, congrats on the project

twsouthwick commented 5 months ago

For compliance reasons I can't use the custom feed (GitLab CI/CD pipeline at on-premise server without external access)

Remember NuGet.org has releases from anyone - there is no vetting there. If you (or your team) thinks something is more secure/stable/etc by virtue of being on NuGet.org, you should rethink that.

As for releasing on NuGet.org, we could potentially do that. However, I expect if using custom feeds are a concern, you can vet it however you need and injest it into your own feed so that it is "trusted" for your org.

my team and customer won't feel comfortable with a pre-release tag

There is not a prerelease tag on v0.1.0, v0.2.0, etc, but it is still in initial development. I'm following semver here, and don't plan on releasing a v1.0.0 until I'm confident there's some stability in the tooling and integration APIs.

gumbarros commented 5 months ago

Remember NuGet.org has releases from anyone - there is no vetting there. If you (or your team) thinks something is more secure/stable/etc by virtue of being on NuGet.org, you should rethink that.

100% agree with you, but it's not a policy from my company, it's from the customer, it's more easy to download the NuGet package than open a ticket telling to allow a new URL

There is not a prerelease tag on v0.1.0, v0.2.0, etc, but it is still in initial development. I'm following semver here, and don't plan on releasing a v1.0.0 until I'm confident there's some stability in the tooling and integration APIs.

Thanks, sorry for the confusion

twsouthwick commented 5 months ago

We can aim to get v0.5.0 out on NuGet - should be more stable by then

twsouthwick commented 5 months ago

Is this working for your customer? If it's a blocker for them, we can push to get something out sooner than later; it's an unfortunate policy, but not uncommon unfortunately.

gumbarros commented 5 months ago

Is this working for your customer? If it's a blocker for them, we can push to get something out sooner than later; it's an unfortunate policy, but not uncommon unfortunately.

We are in the study stage for future sprints and see if it's worth the upgrade to CoreWebForms, the project is very big and critical. No need to accelerate your development for the next version /NuGet release, thank you very much. But I can guarantee you that it is a impediment for us not having a NuGet feed.