CSLA version confusion

TSF posted on Monday, February 25, 2013

A few months back I downloaded what appears to be version 4.5.3.0. But the new download page on GitHub seems to indicate that the latest stable version is 4.5.10 and the latest beta version is 4.5.12. Am I looking at something wrong? How did the version go backwards? Is it normal for release version numbers to be behind the beta/RC version numbers?

richardb replied on Monday, February 25, 2013

4.5.Three < 4.5.Ten < 4.5.Twelve

TSF replied on Monday, February 25, 2013

Duh...I wasn't thinking in those terms. Thinking instead of decimals for some reason. Thanks.

RockfordLhotka replied on Monday, February 25, 2013

I've adopted a version numbering scheme that I hope will be consistent for a long time to come.

Ideally I'd use the build number - something like 4.5.1.x and increment 'x' for small changes.

But not all the Microsoft platforms (notably Silverlight) honor the build number, so it turns out to be useless.

As a result, all I have to work with is major.minor.revision

Major and Minor are pretty easy - I try to keep those in sync with the primary .NET framework version I'm targeting.

And that leaves Revision to cover everything else - like adding support for WP8, or mono, or ...

My scheme then is this:

• If the Revision ends in a zero (such as 10, 20, 30, etc.) that's a release
• If the Revision ends in a non-zero (such as 11, 12, 23, 42, etc.) that's a pre-release building toward the next zero ending

So right now I'm prepping 4.5.13, which is a pre-release for the upcoming 4.5.20 release.