If this is your first visit, You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
I think it was up when you were away.
edit: maybe 13 was to fix 12?
"Well, I think that's the initial B2K server release. We saw an update for the 64 slot servers crashing (R13) and now we are about to see R14 to fix the stated problem."
I have noticed alot of servers have been crashing.
"You cannot have 'slaughter' without having 'laughter'"
"If I had wanted to show off, I would have been a porn star."
"I have a 9in. tongue and I can breathe through my ears."
We never saw R13..... I"m having trouble keeping up now !
Skipping the version 13 in software is usual.
Microsoft did that too, Office 2007 was v12 and Officre 2010 is v14.
The 13 number is skip to avoid trouble caused by this number. It's like Friday 13th :P
Anyway, to be back to B2K, they screwed up real bad... I bought it yesterday and it keep asking me to buy it because apparently I didn't bought it... that BS...
Microsoft did that too, Office 2007 was v12 and Officre 2010 is v14.
The 13 number is skip to avoid trouble caused by this number. It's like Friday 13th :P
Anyway, to be back to B2K, they screwed up real bad... I bought it yesterday and it keep asking me to buy it because apparently I didn't bought it... that BS...
That sucks. You're not the only one from what i can gather.
Where do you put the Bayonet?
Chesty Puller (upon seeing a flamethrower for the first time)
I am all in favor of keeping dangerous weapons out of the hands of fools. Lets start with typewriters.
Frank Lloyd Wright
Microsoft did that too, Office 2007 was v12 and Officre 2010 is v14.
The 13 number is skip to avoid trouble caused by this number. It's like Friday 13th :P
Anyway, to be back to B2K, they screwed up real bad... I bought it yesterday and it keep asking me to buy it because apparently I didn't bought it... that BS...
Don't read too much Triskaidekaphobia into no R13 patch. The way software defects are fixed. The developer checks out of the repository the current environment. He writes a fix. Then he checks it into the repo. When they build a build the build engineer selects all of the fixes to go into that build and then the build machine compiles it. Skipping a build could mean that a fix was committed that was actually bad. I.e while QA'ing the build it was found to have problems or a new fix need to be included in the next release. So they make a new build either without the bad fix or with the bad fix fixed hence no build 13. Contrary to what you say skipping version 13 is not really wide spread in software engineering...
From your helpful QA engineer at Hitachi Data Systems
Don't read too much Triskaidekaphobia into no R13 patch. The way software defects are fixed. The developer checks out of the repository the current environment. He writes a fix. Then he checks it into the repo. When they build a build the build engineer selects all of the fixes to go into that build and then the build machine compiles it. Skipping a build could mean that a fix was committed that was actually bad. I.e while QA'ing the build it was found to have problems or a new fix need to be included in the next release. So they make a new build either without the bad fix or with the bad fix fixed hence no build 13. Contrary to what you say skipping version 13 is not really wide spread in software engineering...
From your helpful QA engineer at Hitachi Data Systems
You work at HDS? I have a few friends in their MA office! Neat!
Though... they label their builds with R, short for Release. It implies that once a build is assigned that number, it's out for distribution to providers. My guess is they put together R13, started sending it out, then caught something game-breaking and had to retract it.
Comment