ReactiveUI.Avalonia

[ChrisPulman]

ReactiveUI.Avalonia Following the PR from Max Katz within ReactiveUI we have now created a dedicated Repository for Avalonia.
We are now ready for a release which will be produced as ReactiveUI.Avalonia in Nuget.
If there is anything further that this project needs to cover then we would welcome any Pull requests.
Max hadn't completed the transfer from Avalonia however we believe that we have now completed the task.

[ChrisPulman]

ReactiveUI.Avalonia Following the PR from Max Katz within ReactiveUI we have now created a dedicated Repository for Avalonia. We are now ready for a release which will be produced as ReactiveUI.Avalonia in Nuget. If there is anything further that this project needs to cover then we would welcome any Pull requests. Max hadn't completed the transfer from Avalonia however we believe that we have now completed the task.

If one of the Avalonia maintainers could give the go ahead for release, we will proceed, thank you.

[maxkatz6]

Looks good to me, but I have a question about versioning.
Do you plan to sync it with Avalonia or with ReactiveUI?

Since it's not part of this repository, you can freely target lowest possible version of Avalonia. I would suggest going with 11.3.0, as that's what we support with bugfixes. But it should work with 11.2.0 or lower too.
And in this case ReactiveUI.Avalonia version can be synced with the rest of ReactiveUI packages.

[ChrisPulman]

So, with regards to versioning, we will revert the initial release of ReactiveUI.Avalonia to 11.3.0, this will contain the latest ReactiveUI version 22.0.1 and related packages along with Avalonia packages 11.3.0, the ReactiveUI.Avalonia Patch version will be manually bumped with each release.
Thereon, any ReactiveUI updates will then bump the Patch number until for example Avalonia 11.4.x is released, we will then bump the Minor to follow and reset the Patch. If you then go with a Major version bump, we will also follow suit in the same manner, therefore we will always have a Major, Minor version match, and releases will only contain the Avalonia latest Major, latest Minor, oldest Patch the end user will be responsible for ensuring they have the latest Patch of Avalonia.

With regards to the tests within ReactiveUI.Avalonia we will test against the latest Major, Minor, Patch release of Avalonia to make sure that no breaking changes occur, this way we can inform you of issues if they arise. Generally, we follow a 2-week lag on package releases so you're more likely to get feedback from your direct consumers first.

I trust this is the approach that you are happy with and have described.
As the Avalonia.ReactiveUI package already has historic versions I don't see any benefit in releasing a new package with an older Avalonia Minor than the latest.
The initial ReactiveUI.Avalonia V11.3.X packages will become a migration point for the end users to transition across until V12.X.X is released.

Please let us know if there is anything you would like differently from this.

[glennawatson]

Be easier if we can match your major minor but patch we'll increment separate

[glennawatson]

Other then that I agree with the rest of what Chris said

[maxkatz6]

Sounds good. I have no issues with that plan.

[maxkatz6]

Thank you!

From the Avalonia side, after it's released, we need to redirect Avalonia.ReactiveUI to ReactiveUI.Avalonia.
Avalonia.ReactiveUI package itself will continue to get updates during 11.x lifecycle for backward compatibility. Until we release 12.0 without Avalonia.ReactiveUI.

[glennawatson]

https://www.nuget.org/packages?q=reactiveui.avalonia&includeComputedFrameworks=true&prerel=true

Released the packages today for your reference.

[maxkatz6]

Deprecated 11.3.x Avalonia.ReactveUI versions, with ReactveUI.Avalonia as suggested alternative.
Thank you!