Drat this two-track stuff
Posted: Sat Sep 13, 2008 7:24 pm
To beta or not to beta - that is the question... Currently there are two versions on FreeNATS doing the rounds; the "current" (v0) and the "future" (v1). Most people are running the recommended current v0 system and so consequently this is the version that the most effort on quick-bug-fixes goes into, it also doesn't get new danger-code added to it and stays pretty static.
All good.
But... v1 is actually nothing more than a genetically-enhanced Frankenstein 0.04.2x-vintage package with appendages crudely bolted on. It's rotten heart therefore continues to have the same defects as v0 but now additionally wrapped and disguised amongst the extra frilly bits.
So... every v0 bug fix also means remembering to fix the same bug in v1 (and in at least one instance vice-versa) except a one line change on line 272 in v0 is often a four-line headache at line 389 in v1.
So... I really want to consolidate everyone onto v1 and concentrate on a single version
But... although v1's core functionality is pretty solid at least for the same type of server-based testing v0 supported the newer functionality may be a different story once it's exposed to the bizarre range of Unicies and Uniclone OSs that FreeNATTERS seem to use.
So... as the man said "the times, they are a changing". I feel the dangerous take-no-prisoners step of releasing v1 as a beta and the recommended version (as well as the VM version) could be just a few nervous sweaty keystrokes away at any moment.
You will of course be able to stick to v0 if you're a "a'int broke why fix it" type and I will continue to offer my lacklustre best-endeavour get-what-you-pay for support levels but the focus would switch to v1.
All good.
But... v1 is actually nothing more than a genetically-enhanced Frankenstein 0.04.2x-vintage package with appendages crudely bolted on. It's rotten heart therefore continues to have the same defects as v0 but now additionally wrapped and disguised amongst the extra frilly bits.
So... every v0 bug fix also means remembering to fix the same bug in v1 (and in at least one instance vice-versa) except a one line change on line 272 in v0 is often a four-line headache at line 389 in v1.
So... I really want to consolidate everyone onto v1 and concentrate on a single version
But... although v1's core functionality is pretty solid at least for the same type of server-based testing v0 supported the newer functionality may be a different story once it's exposed to the bizarre range of Unicies and Uniclone OSs that FreeNATTERS seem to use.
So... as the man said "the times, they are a changing". I feel the dangerous take-no-prisoners step of releasing v1 as a beta and the recommended version (as well as the VM version) could be just a few nervous sweaty keystrokes away at any moment.
You will of course be able to stick to v0 if you're a "a'int broke why fix it" type and I will continue to offer my lacklustre best-endeavour get-what-you-pay for support levels but the focus would switch to v1.