"Paul S. Person" wrote in message news:***@4ax.com...
On Wed, 9 Oct 2013 15:37:39 -0500, "Marty Stanquist"
Post by Paul S. Person
On Wed, 9 Oct 2013 01:26:58 -0500, "Marty Stanquist"
Post by Marty Stanquist Post by Lynn McGuire
Would it not be better to get version 2.0
out the door? Not that I could do it, I am
getting more and more incompetent by the day.
Version 2.0 is going to be a major upgrade for the languages, GUI, host
platforms, targets, tools, and libraries. It's a lot of work. What did you
have in mind for the short term?
If we need to get a new one out, why not just call it "1.10" and be
done with it? At least we wouldn't get people wondering if the project
is dead ...
This, of course, only applies if doing a new minor-version release
would otherwise make sense. And if going from 1.9 to 1.10 wouldn't
To put it another way: reserving "2.0" for a major upgrade is all very
well, but that shouldn't become an excuse for not doing
otherwise-appropriate releases in the meantime.
I'm leaving the above as-is; from my understanding of the matter, you
aren't quoting properly: the stuff you quote needs a level indicator,
and, by including the entire post, you included my sig, which caused
Post by Paul S. Person
* Release 2.0 will be a major upgrade.
* Intermediate release 1.10 is appropriate.
* And sure, we're bound to break something.
I'll try to complete work on a test Perforce server ( using one of my test
machines) with the latest Perforce server release. Hopefully, this will tell
us how difficult revision 1.10 will be.
which is all very irritating.
But enough griping.
My point was that some tests may be for an OW version greater than,
say, "1.3", and might fail if they only check the first decimal digit,
since "1.10" would be treated as "1.1", which is less than "1.3",
although release 1.10 almost certainly would work properly if release
And I thought there was a well-known (well, to those who have done it
before, anyway) procedure for producing a new release.
"Nature must be explained in
her own terms through
the experience of our senses."
I know, it's a hurdle. I have the procedure and it requires P4V, and thus a
server upgrade. I'm trying to dry run the upgrade and build on a test
machine to see what will break. I'm hoping that any problems will be minor.