Shoutbox

msgplus is hopping from 2.21.57 to 2.50, just in 1 step ....
i was just wandering why the next step is 2.50 and not 2.22 for example
or were there other version that never got to see daylight?

I think it's 2.50 now because it has some big changes... new features, 2.22 is more for smaller changes..

fair enough, but even then the more logical choice would be 2.30
correct?

naaah then it still looks like 2.21.. 2.50 has more impact..

quote:

---

Originally posted by Necroman
fair enough, but even then the more logical choice would be 2.30
correct?

---

yes, but originally the next version after 2.10 was going to be 2.50. Patchou decided that number because that version (2.50) would contain a lot of new features. Then Micorsoft released messenger 6, and Patchou made 2.20 because he wanted Plus! to be compatible with msg 6 but didn't make all those new features.

The last weeks, Patchou have been working a lot in the new version of plus! He added a lot of new features and corrected a several bugs, so the new version is more than a 2.30 version. That version will be 2.50 and will be released on 28th.

Now you can ask: and why not version 3 if patchou added all those new features? Well, I think a version 3 is much more than adding new features. The next version (2.50) will have the same (well, similar) interface as the current one (2.21). Also it'll use the same ways to hook messenger, the same "internal engine". A major number change (from 2.x to 3) should be done (in my opinion) when things related to internal structure of Plus! change.

for instance, a complete rewrite of the code (like there was from 1.42 > 2.0)

From what I learned when I was programming (long ago in a land far, far away ), the unofficial way to build a version number was:

x.y.z (which today is often seen as x.yz)

x = Major verion number: this number should be incremented only when there is a major modification to the core function of the program

y= Minor version number: this number should be incremented when substantial changes are made to the program but without modifying it's core, such as adding features, redesinging the interface, etc.

z= Program revision: This number should be incremented when small changes are made to the program. Such changes can include visual tweaks, bug fixes, security patches, or slight enhancements.

Keep in mind, these are loose guidelines I was told in college, but I've found they apply at least partially to most programs.

Cheers!

randomly made up... lol kidding, they have there own methods

They're good guidelines, yes. But each program and each programmer aplies them in the better way to its features and necessities

Yep, the x.y.z guidelines written here are what I use. The only problem with the "major" version number part is that too much software tend to abuse it to get people to think that the software has major new features when in fact, only some bitmaps and a few options were added. Using that kind of standard I would probably be at version 4.0 already but hey, I think that "2.50" looks very sweet