Our top-notch team of developers has developed a new way for our official version and our beta version(s) to live their own lives :)

iStripper version 1.2.546, released today, gives you the possibility to switch from the official version (named 'stable') to the Beta version and vice-versa.

Please note that each of these versions will have its own updates as they belong to two separate development "branches".

It also means that you will get the update pop-up information ONLY for the version you are on.

Of course we will keep on publishing any new version ("Stable" or "Beta" branches) here on the forum and on Discord :)

For your own comfort, I highly recommend that you update to version 1.2.546 now :

A question : 1.2.546 is a stable or beta version ?

A question : 1.2.546 is a stable or beta version ?

1.2.546 - Build 1000, is both a beta and stable. There's currently no difference between the 2 versions, they're the exact same binary file. However, they are bound to evolve in different directions with time.
Do note that, for the beta branch, a version will be identified by the combination of the version number and build number (so 1.2.546 - Build 1001 will be different from 1.2.546 - Build 1000). For the stable version, the version number will always be incremented for easier understanding.

Do note also, that every bug that is corrected in the stable version will also be in the beta version. The opposite isn't always true, as some bugs that are deemed not critical in a beta version won't warrant the release of a new stable version on their own, if that makes sense.

@guillaume
Thank you, it's clearer now 👍

Question:

When a New Stable version with a new Version number is Released.
Does the Beta Branch, then also Update to the Same Version number?

So we might have:
1.2.546 Stable version Branch
1.2.564 1000 Beta Branch
1.2.546 1001
1.2.546 1004
1.2.546 1010

then
1.2.548 new Stable version Branch
1.2.548 1000 Beta Branch
1.2.548 1001
1.2.548 1004
1.2.548 1010

@Wyldanimal

In the general case, the beta will switch version before the stable one, however those version numbers and build increment will remain at our discretion, usually following some intuitive pattern.

So the next beta will probably be 1.2.547, starting at build 1000 let's say. Say we have 2 beta versions til 1.2.547 goes to stable, that should be build 1.2.547 build 1002 when it goes to stable. At this point, the next beta will be version 1.2.548, probably build 1000 again. Now let's say on that beta there's a new feature, which still has some bugs that are being corrected on the branch before rolling out to stable, that will be 1.2.548 build 1001, 1002 etc. If in the meantime we correct some important bugs on the stable only, the stable will become 1.2.548 build 1003 (or whichever else is available), and the beta will change to 1.2.549 in the meantime.
Generally, the beta will have the next version number that will be released to stable, which will be updated whenever the stable has a version increment, whether or not that latter version has been rolled in beta beforehand.

That's the general idea, though it's not set in stone and is subject to revision for any reason in the future. In actuality, the build number is mainly for us to release beta versions without changing their version numbers, and shouldn't be given too much thought besides identifying an increment on a version, and making the previous build numbers irrelevant on a given version.

Hope that makes sense.