06-13-2022, 07:40 PM
(06-13-2022, 07:18 PM)bplus Wrote: QB64 has picked up a fork in development. .com people are still with last version QB64 2.02. PE people have option to get version v.0.8.2 fixed v 0.8.0 of the $ in filename or path and the v 0.8.1 blunder with Compiler options. Getting v 0.8.2 will give option to compile from optimized setting from the IDE like you could do from command line. Also has all the fixes for the Wiki in Help from earlier updates since the fork. I don't know what .com people are doing for IDE Help???and
(06-13-2022, 07:29 PM)SMcNeill Wrote: https://qb64phoenix.com/forum/showthread.php?tid=259 -- Read this. It explains the logic behind our version numbers.
TLDR: Basically, we branched off the development build. Any version after 1.0 should be a *stable* build, in my opinion, and we didn't feel we could promise that, as we weren't the ones involved with whatever was in the development build. We weren't certain about what they'd finished working on, and what was still being worked on. Since we were sorting out the glitches and all that came from server swapping and such, we swapped over to calling our version "Phoenix Edition" and the 0.x version numbers.
We're branched off of -- and built on top of -- version 2.0.2 development. Think of us as going from Windows 98 to Windows Vista, except we went from QB64 to QBPE. New team, new fork, new version number -- same base product + enhancements, at the end of the day. ?
Aha, OK. That at least makes sense.
Thanks guys for explaining!
PS I just saw this - it seems I wasn't the only one confused, so now I don't feel so bad!
the apocalypse!