[Discussion] Release schedule

[jsmarcus]

Is there any release schedule or plan to release more than just the Effects toolkit to nuget?

[jamesmontemagno]

Yes! Getting ready to re-boot this.. We haven't actually released anything official, someone uploaded it randomly :(

[jsmarcus]

Please let us (the community) know what/how we can help.

[jfversluis]

It still makes sense to agree on a structured release schedule. Let's discuss here!

[SunnyMukherjee]

Are you guys planning to release the first NuGet ahead of Maui or with Maui? I figured we can have a small set of the most common items, including converters, effects, behaviors, validators, etc. that are easier to implement than some controls, which can be released in future versions. In this way, we can start using it in our projects sooner. Thoughts?

[jfversluis]

Hey @SunnyMukherjee thanks for pitching in! We definitely plan on doing something before .NET MAUI. In fact, I want to release an initial version ASAP. This way people can benefit today and we can start getting community involvement.

This will most certainly not wait for a next major release. We will however, hopefully evolve together with the Xamarin space :)

[Cfun1]

@jfversluis should this be moved to a discussions rather than issues?

[jfversluis]

In fact I'm closing this for now. Let's see how development progresses first. If we set a release schedule to every 6 weeks but we only have a handful of minor things that are fixed than pushing out releases makes no sense. For now I think we'll roll with how we feel about a new release. If that turns out to be problematic in the future we can reevaluate.

[IeuanWalker]

@jfversluis could you automate the releases? i.e. whenever something is committed to the main branch it will build and release a beta or a preview version.

That way if a feature is added or a bug is fixed, it can be used straight away rather than waiting for a release.

[Cfun1]

@IeuanWalker Maybe it already implemented check this bot message for example #725 (comment) also take a look at #507

[IeuanWalker]

@Cfun1 thanks but the issue with that it's hard to use a package locally in a team, everyone will need to know to set up a new package source pointing to a local folder.

But most importantly it brakes automated builds, as it tries to pull the NuGet package from NuGet rather than the local folder.

Might be wrong, so would be good to know if there is a different way around this.