[2.0] Plans for Blazorise versions and future

[stsrki]

I will write down our plans for Blazorise 2.0 in this ticket.

The general plan is to release 1.7 sometime in October 2024. This version will introduce some new components(like PdfViewer, and Skeleton) and minor API cleanups while making existing APIs obsolete.

After that, we will start working on the next major version, 2.0. With 2.0, we plan to clean major APIs that we believe will improve our users' QoL—starting with #5596. Then all obsolete APIs will be removed.

---

In parallel with cleaning and improving the component APIs, we also plan to drop support for older .NET versions.

The plan is to remove

• NET6
• NET7

and keep

• NET8
• NET9 (once it is released)

Older .NET versions keep us from improving Blazorise in some areas, so this is the perfect time to do it. NET 8 is also marked as LTS, so for the majority of our users, it should be fine. Hopefully.

---

All these changes will obviously, as usual, be written down in our release notes with all migration steps clearly described.

[stsrki]

We don't know how long 2.0 can take until finished since there will be many changes needed. So, to allow for releases of 1.8 and 1.9 in between, we will use the following branch and merge strategy.

1. Everything that has a breaking change will go into the next-2.0 branch
2. Everything that improves Blazorise or adds a non-breaking change will go into the master branch

graph LR
    B(New Feature)
    B --> C{Decision}
    C -->|breaking change| D[next-2.0 branch]
    C -->|non-breaking change| E[master branch]

Loading

If there are enough features in the master branch to justify a new release, we will make it work and release 1.8, and/or 1.9.

[pvanroos]

Does Blazorise currently support .NET 9?

[stsrki]

Does Blazorise currently support .NET 9?

Yes, it supports it.

[pvanroos]

Ok. I had a problem with components that don't have parameterless constructors. You can now inject objects into the constructor in .NET 9 for Blazor component classes. I'll log it in the issues.

#5875