Are we going to have a 13c & 13d?

[Runelaron]

<DIV>Due to the delay of patch 13a & b till sept 12th. Are we going to have a 13c and 13d in place of the planned 14a and 14b?</DIV>

[Fayline Fyrecat]

Moorguard posted the update schedule, check the Dev Tracker.  Now, I'm not trying to sound mean, but does it matter?  <DIV>Whether they call the updates 13a, 14c, or 2324catfish they still just push out updates once they've passed the initial internal testing.  I doubt we'll be "missing" any improvements due to the long period of time dedicated to LU13.  If it's ready to be pushed out during this time, it will be lumped into LU13.  What's not ready will be in the next update LU14 whenever it's time comes.</DIV> <DIV> </DIV> <DIV>As M- or B-guard said, Test will be receiving MANY updates between now and Sept. 12; and I doubt they'll bother to label each one as LU13a, b, or c.  It's just a label and I'm sure they're more concerned with content than labeling.</DIV> <DIV> </DIV> <DIV>Again, please don't take this as a flame :smileyhappy: , but they'll be pushing out updates as they're ready; what they decide to label them probably doesn't have any bearing on the content therein.</DIV>

[Cuz]

They really should call the combat update 2324catfish. It would be the single greatest moment in my EQ2 boards history.

[Naginata]

<P>2550catfish YOU NOOB!@@*@*@#*@*</P> <P> </P> <P>GET OFF TEH BORDZZZ!!!!!!!</P>

[Eyes_of_Truth]

<P>Well what ever you want to call it, it's onthe test patcher NOW hehe... and test server is currently down as of posting this, but who CARES! IT's HERE :smileyvery-happy:</P> <P>Toodles!</P>

[WuphonsReach]

<blockquote><hr>Runelaron wrote:<DIV>Due to the delay of patch 13a & b till sept 12th. Are we going to have a 13c and 13d in place of the planned 14a and 14b?</DIV><hr></blockquote>Fayline covered most of it.In general, Test gets the majority of a planned update in one fell swoop (i.e. Test Update #10). Or, if only part of it is ready, they split it into an 11a/11b style and patch it in a few days apart. In between these "big" patches, we also receive daily patches that fix issues discovered on the previous day or two. Most of those downtimes are only 20-40 minutes, rather then the 1-2 hours of a "big" patch.Which also brings us back to the "golden hour" (wrong term?) theory of software development.When a developer makes a change to a section of code, there is a short time window during which changes/corrections can be made quickly and efficiently. Once you get beyond that window, the developer has to spend a lot more mental effort and time trying to understand how to fix a particular bug. Once you get substantially past that time window, management now gets involved and the bug has to be severe enough to warrant spending time and risk touching a piece of code again.This is one of the reasons that a full-time tester population is a desireable trait for a testing server. The faster that you can discover NEW bugs and feed them back to a developer who recently caused the bug to happen, the more likely that the fix will get done quickly and that it will be correct. I've seen it quite a few times, and here's a generalized case history:- Bugs that get reported on the first night after a change, almost always get fixed within 24-72 hours. The coder has apparently not be reassigned to work on something else yet. The only time this doesn't seem to happen is in cases where it's a planned change, or the fix will take more then a few hours. (And not all /bugs are bugs...)- Bugs that don't get reported until a day or two after the change that caused them will often not get fixed before the patch goes live (or, they will apply the fix to the Live patch without Test getting a chance to confirm that it is/isn't fixed).- Bugs that remain uncovered for more then a week tend to get "scheduled" and "prioritized". Which means they may never get fixed, until there is a spare moment in the developer's schedule. Long term bugs have to be sorted out, and scarce resources allocated. Those usually get scheduled for future Live Updates.