Maintenance for the week of February 23:
· [COMPLETE] NA megaservers for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)
· [COMPLETE] EU megaservers for maintenance – February 23, 9:00 UTC (4:00AM EST) - 17:00 UTC (12:00PM EST)
· [COMPLETE] ESO Store and Account System for maintenance – February 23, 4:00AM EST (9:00 UTC) - 12:00PM EST (17:00 UTC)

8+ hour patch .. this is why you don't rush a content patch on a non-scheduled day

  • kitsinni
    kitsinni
    ✭✭✭✭✭
    Bromburak wrote: »
    kitsinni wrote: »
    Bromburak wrote: »
    kitsinni wrote: »
    8+ hour patch .. this is why you don't rush a content patch on a non-scheduled day

    Source of rushing purpose?

    Less than 24 hours before the patch was out they confirmed in this thread it was tenative and not ready yet http://forums.elderscrollsonline.com/discussion/comment/1023634/#Comment_1023634

    That is your defintion of "rushing" but reality looks as follows:
    Hi, folks. We announced that we wanted to push version 1.2.3 this week to bring you all our next major content update. The build wasn't quite ready to go yesterday, so we ended up cancelling our regular maintenance in favor of preforming one today.

    My point is that there was no need for this patch to hit today. There was no game breaking thing that had to be hotfixed. It is a content patch. There was already a maint scheduled for Thursday so what is the rush to have it done today? Obvioulsy it could have used more testing if it is going to take at minimum 250% of expected patch time.
  • ReCreare
    ReCreare
    ✭✭✭
    This is my day off and I expect $0.16 of compensation for the 8 hours I'm unable to play.
  • dharbert
    dharbert
    ✭✭✭✭✭
    ✭✭
    There's no hotfix that was required to immediately correct a game-breaking issue, so this content update could have waited until Thursday.

    And it's glaringly obvious that this update wasn't properly tested before deployment to a live server.

    This is what's going happen, guaranteed. It won't be live until at least 5 or 6 pm. The login server will be swamped for hours when it comes back up, followed by bugs galore and, more than likely, more downtime.
  • Etharian
    Etharian
    ✭✭✭
    kitsinni wrote: »
    Etharian wrote: »
    kitsinni wrote: »
    As of yesterday when they skipped the maintenance ESO said they had tenative plans to push the patch today but it wasn't quite ready. Now after four hours of patching they are expecting at least another four more hours.

    If you are not 100% sure about a major content patch 24 hours before pushing it live you can wait a couple days and test it. It isn't like they have been telling us for weeks to expect it on a certain day. You already have a scheduled day on Thursday what is the rush to push out a patch that wasn't even ready 24 hours ago?

    [Moderator Note: Edited per our rules on Rude and Insulting Comments


    thanks for proving my point.
    Edited by ZOS_UlyssesW on June 24, 2014 7:06PM
  • Frenzypanda
    Frenzypanda
    ✭✭
    This patch is critical for templars and should be pushed out asap. I support it. If you can ask why need to patch today, you should ask yourself why cant you wait a couple of hours today? Unless you have a personal agenda. It is happening during SEA peak hours and it is fine with my guild and myself at least :)
    Edited by Frenzypanda on June 24, 2014 4:59PM
  • demonlkojipub19_ESO
    demonlkojipub19_ESO
    ✭✭✭✭✭
    Could be 8 hours depending on what their definition of "A few hours" is... but oh well either way.
    Edited by demonlkojipub19_ESO on June 24, 2014 5:00PM
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    Etharian wrote: »
    kitsinni wrote: »
    Etharian wrote: »
    kitsinni wrote: »
    As of yesterday when they skipped the maintenance ESO said they had tenative plans to push the patch today but it wasn't quite ready. Now after four hours of patching they are expecting at least another four more hours.

    If you are not 100% sure about a major content patch 24 hours before pushing it live you can wait a couple days and test it. It isn't like they have been telling us for weeks to expect it on a certain day. You already have a scheduled day on Thursday what is the rush to push out a patch that wasn't even ready 24 hours ago?

    [Moderator Note: Edited per our rules on Rude and Insulting Comments


    thanks for proving my point.

    You are welcome
    Edited by ZOS_UlyssesW on June 24, 2014 7:06PM
  • crislevin
    crislevin
    ✭✭✭✭✭
    This patch is critical for templars and should be pushed out asap. I support it. If you can ask why need to patch today, you should ask yourself why cant you wait a couple of hours today? Unless you have a personal agenda. It is happening during SEA peak hours and it is fine with my guild and myself at least :)
    lol, its obviously not "couple" of hours. If you consider the work schedule of players, and the download coming up, it maybe 24 hrs for some.
  • Themotherpotato
    Lol lets go for 24houers downtime Zenimax you know people are going to Love you!Gogogogog
  • nerevarine1138
    nerevarine1138
    ✭✭✭✭✭
    ✭✭✭✭✭
    dharbert wrote: »
    There's no hotfix that was required to immediately correct a game-breaking issue, so this content update could have waited until Thursday.

    And it's glaringly obvious that this update wasn't properly tested before deployment to a live server.

    This is what's going happen, guaranteed. It won't be live until at least 5 or 6 pm. The login server will be swamped for hours when it comes back up, followed by bugs galore and, more than likely, more downtime.

    The update was tested on the PTS before being deployed.

    Sometimes (now, stay with me here) things take longer than expected. Even if you test out an update a million times on the test server, the actual update can be delayed. Oh, and by the way, I've never experienced a login queue in this game, including right at launch. That's the one thing we really don't have to worry about.

    But most importantly: it's a game. You'll live.
    ----
    Murray?
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    This patch is critical for templars and should be pushed out asap. I support it. If you can ask why need to patch today, you should ask yourself why cant you wait a couple of hours today? Unless you have a personal agenda. It is happening during SEA peak hours and it is fine with my guild and myself at least :)

    Like I said earlier my concern is not with the amount of time it takes to patch, my concern is if the patch was ready or not. If they were unsure about it 24 hours before patching I just can't believe that enough testing could have been done to make it ready for live. My main concern is with the end result, how many bugs are we going to be dealing with once the patch is applied if it wasn't even tested enough to patch correctly?
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    dharbert wrote: »
    There's no hotfix that was required to immediately correct a game-breaking issue, so this content update could have waited until Thursday.

    And it's glaringly obvious that this update wasn't properly tested before deployment to a live server.

    This is what's going happen, guaranteed. It won't be live until at least 5 or 6 pm. The login server will be swamped for hours when it comes back up, followed by bugs galore and, more than likely, more downtime.

    The update was tested on the PTS before being deployed.

    Sometimes (now, stay with me here) things take longer than expected. Even if you test out an update a million times on the test server, the actual update can be delayed. Oh, and by the way, I've never experienced a login queue in this game, including right at launch. That's the one thing we really don't have to worry about.

    But most importantly: it's a game. You'll live.

    ZOS stated less than 24 hours before pushing it to live it wasn't ready and there are parts added in that were not on the PTS. If they waited for it to be tested further then it's a game. You'll live.
  • Frenzypanda
    Frenzypanda
    ✭✭
    I predict it will be done by NA peak hours. We from SEA dont get to play from evening onwards. But imagine all the goodies that are coming? Faster weapon swap, templars can dps in 12man, updates to all classes. It will be worth it.
  • kieso
    kieso
    ✭✭✭✭✭
    8 hrs is pretty long for a primary server to be down.
  • Aett_Thorn
    Aett_Thorn
    ✭✭✭✭✭
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?
  • DeLindsay
    DeLindsay
    ✭✭✭✭✭
    kitsinni wrote: »
    If you are not 100% sure about a major content patch 24 hours before pushing it live you can wait a couple days and test it.

    Yes because Blizzard, Trion, CCP and every other company does what you just said. You literally cannot test everything to be 100%, it's impossible. And I gotta lol at all the crying on the forums about DT's. Nobody bothers to remember the WEEKS of problems WoW had after a minor content patch (that had the servers down for 24 hours).
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    Aett_Thorn wrote: »
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?

    No it is like calling your mechanic and saying I think I need an oil change soon. Your mechanic demands you bring it in right then, then says I'm waiting on a delivery of oil so your car will be in the shop for a day. Then you ask why did I have to bring it in right now then?
  • Aett_Thorn
    Aett_Thorn
    ✭✭✭✭✭
    DeLindsay wrote: »
    kitsinni wrote: »
    If you are not 100% sure about a major content patch 24 hours before pushing it live you can wait a couple days and test it.

    Yes because Blizzard, Trion, CCP and every other company does what you just said. You literally cannot test everything to be 100%, it's impossible. And I gotta lol at all the crying on the forums about DT's. Nobody bothers to remember the WEEKS of problems WoW had after a minor content patch (that had the servers down for 24 hours).

    Because people tend to be short-sighted when looking back. People expect new games coming out to be just as good and have just as much content as games that have been out for 8+ years, but refuse to remember the growing pains those same games had.
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    DeLindsay wrote: »
    kitsinni wrote: »
    If you are not 100% sure about a major content patch 24 hours before pushing it live you can wait a couple days and test it.

    Yes because Blizzard, Trion, CCP and every other company does what you just said. You literally cannot test everything to be 100%, it's impossible. And I gotta lol at all the crying on the forums about DT's. Nobody bothers to remember the WEEKS of problems WoW had after a minor content patch (that had the servers down for 24 hours).

    I can't remember a single time where Blizzard publically announced a patch wasn't ready 24 hours before pushing it on a non-scheduled day.
  • Jimm_ay
    Jimm_ay
    ✭✭✭
    Aett_Thorn wrote: »
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?

    It's more like you bought a car and drove it off the lot and the doors fell off. And they tell you "we will get them doors back on soon, just keep paying the loan."
  • nerevarine1138
    nerevarine1138
    ✭✭✭✭✭
    ✭✭✭✭✭
    kitsinni wrote: »
    Aett_Thorn wrote: »
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?

    No it is like calling your mechanic and saying I think I need an oil change soon. Your mechanic demands you bring it in right then, then says I'm waiting on a delivery of oil so your car will be in the shop for a day. Then you ask why did I have to bring it in right now then?

    That may be the single worst analogy I've ever read anywhere.

    The patch was supposed to be applied yesterday. They realized it wasn't ready yet. So they delayed it and put it up today. It happens to be taking longer than expected. As things tend to do when computers are involved. No analogies needed. No hyperbolic threads declaring that this is a sign of the end times needed. Just a simple delay.
    ----
    Murray?
  • Ifthir_ESO
    Ifthir_ESO
    ✭✭✭✭✭
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    The truth is that it was just a terrible PR move to publically announce that the patch wasn't ready to go and then push it so soon after.
  • wraith808
    wraith808
    ✭✭✭✭
    kitsinni wrote: »
    ZOS_GinaBrunoadmin

    June 23Staff Post



    Hey there, everyone. What Jessica said is correct - we are tentatively scheduled to release update v1.2.3 starting tomorrow. That said, we are still testing the build and want to wait until we're completely sure it passes before announcing the maintenance. We should have news for you very soon, and we'll message it out as soon as we know!

    I guess this means something different to you guys /shrug

    It does. And it would to you also if you knew about development. Testing the build means that it's been built and is ready. They just had some more testing to do for sanity's sake. You know... being thorough. Testing the build has next to nothing to do with the actual deployment and problems that may occur at that point.

    The more you know...
    Edited by wraith808 on June 24, 2014 5:37PM
    Quasim ibn-Muhammad - VR 12 Redguard Dragon Knight
    Taladriel Vanima - VR 5 Altmer Nightblade
    Ambalyo iyo Bogaadin - VR 1 Redguard Sorceror
  • DeLindsay
    DeLindsay
    ✭✭✭✭✭
    Ifthir_ESO wrote: »

    AHAHAHAHAHAHA!!
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    kitsinni wrote: »
    Aett_Thorn wrote: »
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?

    No it is like calling your mechanic and saying I think I need an oil change soon. Your mechanic demands you bring it in right then, then says I'm waiting on a delivery of oil so your car will be in the shop for a day. Then you ask why did I have to bring it in right now then?

    That may be the single worst analogy I've ever read anywhere.

    The patch was supposed to be applied yesterday. They realized it wasn't ready yet. So they delayed it and put it up today. It happens to be taking longer than expected. As things tend to do when computers are involved. No analogies needed. No hyperbolic threads declaring that this is a sign of the end times needed. Just a simple delay.

    So being the absolute worst analogy in the history of humanity .. why did the patch need to be pushed today? They never announced it was supposed to be pushed yesterday until today. We were never given a time to expect the patch other than hopefully this weak. What would have been so terrible about pushing it on Thursday and actually testing it for a couple days after the thought they had it fixed?
  • Scanster1
    Scanster1
    ✭✭
    Well, I have to agree with all the comments. If it's not ready, don't push it. But then you're forgetting something else here to complain about. As with all patches, there will be a patch to fix the patch that fixed the original patch. AND since it wasn't really ready and was pushed....there will be a patch to fix the patch that fixed the patch of the original patch. So, chin up to all you complainers out there. More complaining fun is on the horizon!! Weeeeeeeeeeeeeee.
  • nerevarine1138
    nerevarine1138
    ✭✭✭✭✭
    ✭✭✭✭✭
    kitsinni wrote: »
    kitsinni wrote: »
    Aett_Thorn wrote: »
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?

    No it is like calling your mechanic and saying I think I need an oil change soon. Your mechanic demands you bring it in right then, then says I'm waiting on a delivery of oil so your car will be in the shop for a day. Then you ask why did I have to bring it in right now then?

    That may be the single worst analogy I've ever read anywhere.

    The patch was supposed to be applied yesterday. They realized it wasn't ready yet. So they delayed it and put it up today. It happens to be taking longer than expected. As things tend to do when computers are involved. No analogies needed. No hyperbolic threads declaring that this is a sign of the end times needed. Just a simple delay.

    So being the absolute worst analogy in the history of humanity .. why did the patch need to be pushed today? They never announced it was supposed to be pushed yesterday until today. We were never given a time to expect the patch other than hopefully this weak. What would have been so terrible about pushing it on Thursday and actually testing it for a couple days after the thought they had it fixed?

    As explained earlier, deploying a patch is a different process than testing a build. You can test a build forever, but that doesn't mean that it will deploy without a hitch.

    They wanted to get the patch out yesterday. They couldn't, so they pushed it to today. Unless they declared today a holiday of some kind, I fail to see why this is such a big deal.
    ----
    Murray?
  • kitsinni
    kitsinni
    ✭✭✭✭✭
    kitsinni wrote: »
    kitsinni wrote: »
    Aett_Thorn wrote: »
    I liken complaints like this to taking your car to a mechanic to get it fixed. The mechanic calls you and tells you that they're waiting on a part, and your car won't be ready until tomorrow. Then the next day he calls and says that he is working on your car, but it won't be ready for a few hours. Then you complain that if the car wasn't ready yesterday, how could it possibly be ready today?

    No it is like calling your mechanic and saying I think I need an oil change soon. Your mechanic demands you bring it in right then, then says I'm waiting on a delivery of oil so your car will be in the shop for a day. Then you ask why did I have to bring it in right now then?

    That may be the single worst analogy I've ever read anywhere.

    The patch was supposed to be applied yesterday. They realized it wasn't ready yet. So they delayed it and put it up today. It happens to be taking longer than expected. As things tend to do when computers are involved. No analogies needed. No hyperbolic threads declaring that this is a sign of the end times needed. Just a simple delay.

    So being the absolute worst analogy in the history of humanity .. why did the patch need to be pushed today? They never announced it was supposed to be pushed yesterday until today. We were never given a time to expect the patch other than hopefully this weak. What would have been so terrible about pushing it on Thursday and actually testing it for a couple days after the thought they had it fixed?

    As explained earlier, deploying a patch is a different process than testing a build. You can test a build forever, but that doesn't mean that it will deploy without a hitch.

    They wanted to get the patch out yesterday. They couldn't, so they pushed it to today. Unless they declared today a holiday of some kind, I fail to see why this is such a big deal.

    Ok granted deploying and testing are differnet, but with virtual servers it is extremely easy to test deployment as well. Regardless why did it need to be pushed today? What was this extreme urgency that couldn't wait till the scheduled day?
  • kaosodin
    kaosodin
    ✭✭✭✭
    chill. these rants are so old.


    Sooo old dude. Its seriously ruining the forume for me, all I see is negativity or selfish post

This discussion has been closed.