Telerik UI for ASP.NET Core versioning feedback

5 Answers 291 Views
General Discussions
Telerik Admin
Top achievements
Rank 1
Iron
Telerik Admin asked on 11 Nov 2022, 04:09 PM
We need your feedback, because we are considering changes in the release approach for Telerik UI for ASP.NET Core. Please provide your feedback in the comments section below:


1. Is it hard to understand the version numbers of our releases? If yes, what makes them hard to understand them?

2. Would semantic versioning (SemVer) of our releases make it easier to understand our version numbers and what's behind them?

3. If we go with SemVer, we might need to start with version 3000.0.0 as we currently use 2022.x.x. Please share your thoughts about this approach and ideas for what number versioning would work best for you.

Taras
Top achievements
Rank 3
Iron
Iron
Veteran
commented on 23 Nov 2022, 08:05 PM

I think current versioning system is fine.
Fernando
Top achievements
Rank 2
commented on 21 May 2023, 08:21 AM | edited

Versioning is fine. Thanks
Gordon
Top achievements
Rank 1
Iron
commented on 27 Jul 2023, 10:17 PM

I think current versioning system is fine. Don't change what isn't broken.

5 Answers, 1 is accepted

Sort by
0
Francis
Top achievements
Rank 1
Iron
Iron
Iron
answered on 17 Nov 2022, 02:00 PM
I am fine with the current versioning as it is easy to match the subscription period with the chronology of the releases.
0
Walter
Top achievements
Rank 2
Iron
answered on 21 Dec 2022, 11:15 PM
I find this version method easy to use and use it myself. I think it is easier for an end user to tell you version they are on and check it with what it should be. I look at it and can say that there should be a newer version just on the date of what I am using. Version numbers that are SemVer give you no way to know if there should be a newer version because there is no reasoning to the version number other than it increments up.
0
NoobMaster
Top achievements
Rank 2
Iron
answered on 08 Apr 2023, 06:03 AM
no problem with current versioning, its understandable.
0
Andi
Top achievements
Rank 1
Iron
Iron
answered on 26 Apr 2023, 12:49 PM
The versioning works fine and its understandable.
Dave
Top achievements
Rank 2
Iron
Iron
commented on 02 May 2023, 03:29 PM

The versioning is fine, but dependencies could use some attention.  I recently upgraded to 2023.1.425.  According to the dependencies list in the NuGet package manager, Microsoft.CodeAnalysis >= 4.4.0 is required.  I had v4.5.0 installed, and this ended up breaking a lot of the Telerik controls.  I would get a Roslyn "get_Unreachable" error which told me precisely nothing. 

Poking around on the forums, I saw a response from Mihaela that suggested the dependency SHOULD be Microsoft.CodeAnalysis = 4.4.0 (not greater than or equal to).  Once I downgraded, my problems went away.

Now I wish I could get the day back that I spent trying to figure out what was broken.

0
Chris
Top achievements
Rank 1
Iron
answered on 05 Feb 2024, 02:31 AM
HI

Why Telerik UI for ASP.NET Core 2024 Q1 (2024.1.130) installation searching for asp.net.core 2021.3.1207 .msi file ??

Chris
Tags
General Discussions
Asked by
Telerik Admin
Top achievements
Rank 1
Iron
Answers by
Francis
Top achievements
Rank 1
Iron
Iron
Iron
Walter
Top achievements
Rank 2
Iron
NoobMaster
Top achievements
Rank 2
Iron
Andi
Top achievements
Rank 1
Iron
Iron
Chris
Top achievements
Rank 1
Iron
Share this question
or