UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
I'm not a software developer and absolutely no expert here.. How is a commercial software version numbering dertermined?
I generally thought:
1. Major changes move versions from 1.x to 2.x etc.
2. Minor additions move things from x.1 to x.2
3. Enhancements to existing routines move things from x.x1 to x.x2
Â
I guess I'm trying to cut Mabula some slack here. At first glance one could think "all this for 1.082 to 1.083??". I have to admit looking at another software package and seeing it had "only" moved from 1.7x to 1.9x in 3 years and thinking "well, that hasn't seen much development". Looking at another and seeing it move from 2.x to 3.x in the same time made me think "this is more actively developed".
Â
It seems to me (absolutely no complaint as "its just a name" and again I'm no expert), but this last round is more of a 1.8 to 1.9. Is there something more formal at play here or is it just marketing?Â
Â
Â
Â
Hi William @maxtrixbass,
Yes, you make a very valid point here 😉Â
This release could well have been going from 1.083 to 1.1 considering what changed, improved and was added and the long release time.
Rules about version numbering have to do with setting goals I think and there are no set rules really. It depends on the project and the possibilities probably.
I wil discuss this with Vincent and Wouter going forward to make the version number reflect more what happens with Astro Pixel Processor. We will definitely make a clear list of the upcoming future releases and what they will contain and I will publish it on our website.
As far as marketing concerned, version numbering will be used for marketing for sure, so maybe I need to be a bit more aggresive with this?
Thank you very much for your thoughts!
Mabula
Marketing is, like software, not my strong suit, but there is certainly an aspect of "perceived value" here. To me, I look at 1.x versions of any software package as "less mature" than 2.x+. I don't like bleading edge. I just want something that works. I have a feeling there are more of us than the tinkerers who want the latest albiet unproven release or that new gadget that just hit the market. I don't think it unreasonable to call this version 1.9...and I don't mean 1.09. Even looking at those two numbers makes me feel different about APP. Kind of pathetic, but that's why economics is in the social sciences department along with psychology.
I would perceive a small change between "1.082 and 1.083" as a maintenance update really which I think undervalues the work involved, especially with an alpha and 3 betas in the middle. At this rate it could take decades before you hit 1.2.
There are those I'm sure who call a bug fix a major update/rewrite, but you seem to be selling yourself short IMHO.
I was assuming the version number was just iterative. The 83rd releasable build of the software. Each number representing an internal milestone of arbitrary length.Â
That said, I do think a small adjustment conceptually would work. Basically to just drop the 1. and use the build milestone. So this release would be release 83. At work this is how we have evolved to handle build milestones for our customers.
Another approach is the Windows 10 model. Pick a version number and stick to it and give each release a feature version until you move up. Like APP 10 Build 20, 21, 22, etc. then APP 11 Build 20, 21, etc.Â
