Beta Cycle Terminology

[Brent]

I'm trying to explain the beta to a Microsoft MC user and need some help with the terminology.

I'm assuming we call 6.0 and 7.0 new Versions of SageTV
What do we call 6.1, 6.2, 6.3 etc?
And then what do we call 6.1.1, 6.1.2 etc?

I just want to use the proper terminology here. Thanks!

[stuckless]

Originally Posted by Brent

I'm trying to explain the beta to a Microsoft MC user and need some help with the terminology.

I'm assuming we call 6.0 and 7.0 new Versions of SageTV
What do we call 6.1, 6.2, 6.3 etc?
And then what do we call 6.1.1, 6.1.2 etc?

I just want to use the proper terminology here. Thanks!

Brent, you'll probably need a very specific answer from SageTV, but in general, the Build numbers means something like...

MajorVersion.MinorVersion.BuildNumber

Typically a Major Version change signifies a huge change. APIs have changed, been removed, etc. New Major features have probably been added.

A Minor Version would indicate that some smaller features have been added and probably some bug fixes, etc. Possible new APIs are added during a Minor Version update, but no APIs should be removed.

And Finally the BuldNumber would indicate the # of public builds for the given MajorVersion.MinorVersion update. Perhaps some bugs have been fixed, but no new features were added, so the build number increases.

Again, there are many ways to interpret this, and every developer may do something different, so you'll have to wait for Jeff (or someone else at SageTV) for the official meaning of those 3 numbers.

[Bikeman]

M$ Hotfixes = bug fixes. Sage equivalent = x.x.X

M$ Service Packs = collection of hotfixes. Sage = x.X.x

M$ Feature Packs = new features sometimes mixed with bug fixes. Sage = X.X.x

M$ Revisions/Releases = collection of Service and Feature Packs. As in SQL Server 2008 R2 or Windows Server 2003 R2. Sage = ???

M$ 0.0 or model years = major versions. Windows 7 or Office 2010 Sage = X.X.X


These are all Microsoft terminologies maybe they'll understand.

[gplasky]

Originally Posted by Bikeman

M$ Hotfixes = bug fixes. Sage equivalent = x.x.X

M$ Service Packs = collection of hotfixes. Sage = x.X.x

M$ Feature Packs = new features sometimes mixed with bug fixes. Sage = X.X.x

M$ Revisions/Releases = collection of Service and Feature Packs. As in SQL Server 2008 R2 or Windows Server 2003 R2. Sage = ???

M$ 0.0 or model years = major versions. Windows 7 or Office 2010 Sage = X.X.X


These are all Microsoft terminologies maybe they'll understand.

This analogy is even more confusing. I know what you're trying to relate but someone looking at this would think service packs, feature packs or hotfixes need to be applied to affect the Build numbers. And applying these usually doesn't change the build number. (Except for Service packs which usally add an additional SP number to the build and doesn't affect the build number.) It really doesn't relate to MS terminology in this fashion. Sage doesn't do SP. feature packs or Hotfixes (seperate installs of these) It's usually a beta build and then a release build. Stuckless hit the nail on the head with:

MajorVersion.MinorVersion.BuildNumber

• Build being fixes or patches.
• Minor being small features or major bugs fixed. (support new tuner or something broken)
• Major is huge change either to core (APIs) or the way the app works. (new interface)

That simplifies the way Sage does it.

[Brent]

Thanks guys. Excellent explanations. I'll stick with the "major, minor, build" sort of terminology as I talk about them.

[Bikeman]

Gerr,

Didn't say it was right, its just the way M$ does it. If they are a big M$ fanboi and understands M$' terminology, they will understand.

[gplasky]

I know. And I know what you're saying. But it's different enough from what Sage is doing to cause confusion. That's all I was saying. MS is a world unto itself.

Gerry