Maintenance for the week of March 3:
• PC/Mac: No maintenance – March 3
• ESO Store and Account System for maintenance – March 4, 6:00AM EST (11:00 UTC) - 4:00PM EST (21:00 UTC)
• NA megaservers for maintenance – March 5, 4:00AM EST (9:00 UTC) - 11:00AM EST (16:00 UTC)
• EU megaservers for maintenance – March 5, 9:00 UTC (4:00AM EST) - 16:00 UTC (11:00AM EST)
• PC/Mac: No maintenance – March 3
• ESO Store and Account System for maintenance – March 4, 6:00AM EST (11:00 UTC) - 4:00PM EST (21:00 UTC)
• NA megaservers for maintenance – March 5, 4:00AM EST (9:00 UTC) - 11:00AM EST (16:00 UTC)
• EU megaservers for maintenance – March 5, 9:00 UTC (4:00AM EST) - 16:00 UTC (11:00AM EST)
** The problem with the actual patches preceding the patch notes **
onlinegamer1
✭✭✭✭✭
✭
✭
This isn't a thread whining about "gives us the patch notes!!1!one!"
This thread is about the fundamental problem of a software company (ZoS) applying an actual patch (server side and client side) BEFORE the patch notes are created.
Many times, when people have asked ZoS for the patch notes, we were told, clearly and unambiguously, that they actually "finalize" the patch notes on the day of the patch. In other words, the actual patch notes document isn't final. In other words, they don't know what did or didn't make it into the patch, and they haven't come up with the "player-friendly" descriptions of each enhancement or bug fix.
Most of us in the industry know that a bug description can be very technical: "exception E401 in com.classes.player.inventory.junk when bag is full" isn't the kind of thing you want in a patch note, whereas "Fixed an issue where moving an item to junk when your bag was full didn't always work" is more understandable.
But, whenever a bug is being worked on by a Developer, or even if you wait until the bug goes to internal QA, it is at THAT time that you should already be filling in the "patch note" text in the ticket. That way, once that ticket passes QA and makes the final build, the patch notes are already built, and its not subjective or up to a human being to "make" the patch notes, you simply generate a document from the ticketing system, taking the "patch note" field of all tickets which are part of the final build.
This kind of process and automation is something a professional studio such as Zenimax should already have in place. And once again, it has nothing to do with wanting patch notes earlier. It has to do with making sure you KNOW what is being deployed in the patch, so as to minimize errors, false/incorrect patch notes, accidentally reverting previous fixes, and letting something go live that shouldn't.
This thread is about the fundamental problem of a software company (ZoS) applying an actual patch (server side and client side) BEFORE the patch notes are created.
Many times, when people have asked ZoS for the patch notes, we were told, clearly and unambiguously, that they actually "finalize" the patch notes on the day of the patch. In other words, the actual patch notes document isn't final. In other words, they don't know what did or didn't make it into the patch, and they haven't come up with the "player-friendly" descriptions of each enhancement or bug fix.
Most of us in the industry know that a bug description can be very technical: "exception E401 in com.classes.player.inventory.junk when bag is full" isn't the kind of thing you want in a patch note, whereas "Fixed an issue where moving an item to junk when your bag was full didn't always work" is more understandable.
But, whenever a bug is being worked on by a Developer, or even if you wait until the bug goes to internal QA, it is at THAT time that you should already be filling in the "patch note" text in the ticket. That way, once that ticket passes QA and makes the final build, the patch notes are already built, and its not subjective or up to a human being to "make" the patch notes, you simply generate a document from the ticketing system, taking the "patch note" field of all tickets which are part of the final build.
This kind of process and automation is something a professional studio such as Zenimax should already have in place. And once again, it has nothing to do with wanting patch notes earlier. It has to do with making sure you KNOW what is being deployed in the patch, so as to minimize errors, false/incorrect patch notes, accidentally reverting previous fixes, and letting something go live that shouldn't.
8
-
stefan.gustavsonb16_ESO✭✭✭✭✭
✭[deleted for lack of energy to keep discussing a broken process]
Edited by stefan.gustavsonb16_ESO on October 13, 2014 12:33PM4 -
adean27✭✭✭First, 401 error is a client side HTTP access error, so you would NEVER see it in that format.
Second, not a single game company out there finalizes patch notes before implementation. Some release tentative notes ahead of time, but none finalize. ZOS does the same thing, they write tentative notes a couple of weeks ahead and modify them as needed.
Sometimes a server side patch will not be accepted as a certain aspect may not function on a live configuration, so they modify on the fly. Sometimes an item will be completed on patch day and implemented, so they add that too.
If You're in the industry you should know this, you would learn it first week as a QA.5 -
onlinegamer1✭✭✭✭✭
✭First, 401 error is a client side HTTP access error, so you would NEVER see it in that format.
Second, not a single game company out there finalizes patch notes before implementation. Some release tentative notes ahead of time, but none finalize. ZOS does the same thing, they write tentative notes a couple of weeks ahead and modify them as needed.
Sometimes a server side patch will not be accepted as a certain aspect may not function on a live configuration, so they modify on the fly. Sometimes an item will be completed on patch day and implemented, so they add that too.
If You're in the industry you should know this, you would learn it first week as a QA.
1. It was a made up example.
2. "All other companies suck at this process too" is not an argument.
3. You obviously didn't even read the OP, because having the patch note as part of the ticket means it doesn't matter what last minute changes you make, the final list of patch notes is generated from the final list of tickets.
Way to phone in your reply.
[Moderator Note: Edited per our rules on Rude and Insulting Comments]Edited by ZOS_UlyssesW on October 13, 2014 2:49PM3 -
Tabbycat✭✭✭✭✭
✭✭✭So you want them to create some program software that lets them generate patch notes from tickets? How do you know they don't already do this? Perhaps the time it takes them to create the patch notes is actually the time it takes for them to translate all the ticket report mumbo jumbo (as indicated in your OP) into something that's more easily understood by those of us not in the gaming industry.Founder and Co-GM of The Psijic Order Guild (NA)
0.016%1 -
onlinegamer1✭✭✭✭✭
✭So you want them to create some program software that lets them generate patch notes from tickets? How do you know they don't already do this? Perhaps the time it takes them to create the patch notes is actually the time it takes for them to translate all the ticket report mumbo jumbo (as indicated in your OP) into something that's more easily understood by those of us not in the gaming industry.
I know they don't do this, because ZoS (Gina, etc.) have said they make the notes manually (you can search this forum for those replies if you like).2 -
adean27✭✭✭onlinegamer1 wrote: »First, 401 error is a client side HTTP access error, so you would NEVER see it in that format.
Second, not a single game company out there finalizes patch notes before implementation. Some release tentative notes ahead of time, but none finalize. ZOS does the same thing, they write tentative notes a couple of weeks ahead and modify them as needed.
Sometimes a server side patch will not be accepted as a certain aspect may not function on a live configuration, so they modify on the fly. Sometimes an item will be completed on patch day and implemented, so they add that too.
If You're in the industry you should know this, you would learn it first week as a QA.
1. It was a made up example, your point is stupid.
2. "All other companies suck at this process too" is not an argument.
3. You obviously didn't even read the OP, because having the patch note as part of the ticket means it doesn't matter what last minute changes you make, the final list of patch notes is generated from the final list of tickets.
Way to phone in your reply.
Well that escalated quickly...
1. It was to point out that your example is incorrect, which indicates a lack of knowledge in something you are claiming to know quite a bit about.
2. At no point did I indicate that any company "sucked", I indicated that an industry standard is to finalize patch notes once the process has begun. Something you would know working in the industry.
3. I think there seems to be some confusion on what "finalized" means. Just because something is scheduled to be added, does not mean at the last moment that it will in fact be added. As you indicated with your knowledge of the industry, you understand that a Live server configuration is completely different than an in-house system. On various occasions you can get sections of patches that come back corrupt when trying to update, or just do not function with the server side of things as intended, such as modifying functionality. Those things need to be removed, reconfigured, and added in a later patch.
4.
I hope you have a good day.Edited by adean27 on October 13, 2014 12:49PM2 -
TehMagnus✭✭✭✭✭
✭✭onlinegamer1 wrote: »This isn't a thread whining about "gives us the patch notes!!1!one!"
This thread is about the fundamental problem of a software company (ZoS) applying an actual patch (server side and client side) BEFORE the patch notes are created.
Many times, when people have asked ZoS for the patch notes, we were told, clearly and unambiguously, that they actually "finalize" the patch notes on the day of the patch. In other words, the actual patch notes document isn't final. In other words, they don't know what did or didn't make it into the patch, and they haven't come up with the "player-friendly" descriptions of each enhancement or bug fix.
Most of us in the industry know that a bug description can be very technical: "exception E401 in com.classes.player.inventory.junk when bag is full" isn't the kind of thing you want in a patch note, whereas "Fixed an issue where moving an item to junk when your bag was full didn't always work" is more understandable.
But, whenever a bug is being worked on by a Developer, or even if you wait until the bug goes to internal QA, it is at THAT time that you should already be filling in the "patch note" text in the ticket. That way, once that ticket passes QA and makes the final build, the patch notes are already built, and its not subjective or up to a human being to "make" the patch notes, you simply generate a document from the ticketing system, taking the "patch note" field of all tickets which are part of the final build.
This kind of process and automation is something a professional studio such as Zenimax should already have in place. And once again, it has nothing to do with wanting patch notes earlier. It has to do with making sure you KNOW what is being deployed in the patch, so as to minimize errors, false/incorrect patch notes, accidentally reverting previous fixes, and letting something go live that shouldn't.
What QA? xD. I think there's prolly one or two guys doing that. Do agree though that when you use something like Jira or Mantis to manage your open issues/changes, your Patch Notes are pretty much built when you create your version & assign tickets to it.
Maybe they work by sending emails? xD
Honestly all that is going on doesn't really lead me to believe they work like Industry Professionals.0 -
onlinegamer1✭✭✭✭✭
✭onlinegamer1 wrote: »First, 401 error is a client side HTTP access error, so you would NEVER see it in that format.
Second, not a single game company out there finalizes patch notes before implementation. Some release tentative notes ahead of time, but none finalize. ZOS does the same thing, they write tentative notes a couple of weeks ahead and modify them as needed.
Sometimes a server side patch will not be accepted as a certain aspect may not function on a live configuration, so they modify on the fly. Sometimes an item will be completed on patch day and implemented, so they add that too.
If You're in the industry you should know this, you would learn it first week as a QA.
1. It was a made up example, your point is stupid.
2. "All other companies suck at this process too" is not an argument.
3. You obviously didn't even read the OP, because having the patch note as part of the ticket means it doesn't matter what last minute changes you make, the final list of patch notes is generated from the final list of tickets.
Way to phone in your reply.
Well that escalated quickly...
1. It was to point out that your example is incorrect, which indicates a lack of knowledge in something you are claiming to know quite a bit about.
2. At no point did I indicate that any company "sucked", I indicated that an industry standard is to finalize patch notes once the process has begun. Something you would know working in the industry.
3. I think there seems to be some confusion on what "finalized" means. Just because something is scheduled to be added, does not mean at the last moment that it will in fact be added. As you indicated with your knowledge of the industry, you understand that a Live server configuration is completely different than an in-house system. On various occasions you can get sections of patches that come back corrupt when trying to update, or just do not function with the server side of things as intended, such as modifying functionality. Those things need to be removed, reconfigured, and added in a later patch.
4.
I hope you have a good day.
1. Example is absolutely correct. It was not "error 401", it was "Exception E401" a completely made up error. So, again, you're wrong.
2. Again, your argument is "all other game companies do it that way, so should ZoS". That is a logical fallacy called "Appeal to Tradition", and isn't a logical argument.
3. Again, you have to make a build. If you deploy a build and its broken, and you pull out one change/set of changes and re-create the build, then that is the final build. At some point, a build is "final". Something that happens after the "final" build means it WASN'T the final build. Um, derp? So, we now can agree that, at SOME point, the build is... finally final. Finally. In finitum. Done. Ship it. Go time. At THAT point, you can run the patch notes.
Really sick of the fanbois constantly defending ZoS' crappy software practices...4 -
Dominoid✭✭✭✭✭
✭✭I think your too hung up on the word finalizing. The reason you don't get patch notes first is because not all patches or fixes might be "accepted" by the system during update it hasn't happened in a while, but there was a maintenance time early on when they had to scrap the whole patch process because of an error encountered. In your scenario of having them released ahead of time you would have people complaining about not getting something that they were promised. At that point they would have "lost" something.
They aren't typing the patch notes when the patch is being applied. They are waiting to see if the patch is finalized. Not the notes. On the live servers we always get the patch notes before the server is brought back online.
You are being highly critical for no reason of a process that needs to work in the way it does.
Edited by Dominoid on October 13, 2014 1:16PM3 -
Tabbycat✭✭✭✭✭
✭✭✭onlinegamer1 wrote: »onlinegamer1 wrote: »First, 401 error is a client side HTTP access error, so you would NEVER see it in that format.
Second, not a single game company out there finalizes patch notes before implementation. Some release tentative notes ahead of time, but none finalize. ZOS does the same thing, they write tentative notes a couple of weeks ahead and modify them as needed.
Sometimes a server side patch will not be accepted as a certain aspect may not function on a live configuration, so they modify on the fly. Sometimes an item will be completed on patch day and implemented, so they add that too.
If You're in the industry you should know this, you would learn it first week as a QA.
1. It was a made up example, your point is stupid.
2. "All other companies suck at this process too" is not an argument.
3. You obviously didn't even read the OP, because having the patch note as part of the ticket means it doesn't matter what last minute changes you make, the final list of patch notes is generated from the final list of tickets.
Way to phone in your reply.
Well that escalated quickly...
1. It was to point out that your example is incorrect, which indicates a lack of knowledge in something you are claiming to know quite a bit about.
2. At no point did I indicate that any company "sucked", I indicated that an industry standard is to finalize patch notes once the process has begun. Something you would know working in the industry.
3. I think there seems to be some confusion on what "finalized" means. Just because something is scheduled to be added, does not mean at the last moment that it will in fact be added. As you indicated with your knowledge of the industry, you understand that a Live server configuration is completely different than an in-house system. On various occasions you can get sections of patches that come back corrupt when trying to update, or just do not function with the server side of things as intended, such as modifying functionality. Those things need to be removed, reconfigured, and added in a later patch.
4.
I hope you have a good day.
1. Example is absolutely correct. It was not "error 401", it was "Exception E401" a completely made up error. So, again, you're wrong.
2. Again, your argument is "all other game companies do it that way, so should ZoS". That is a logical fallacy called "Appeal to Tradition", and isn't a logical argument.
3. Again, you have to make a build. If you deploy a build and its broken, and you pull out one change/set of changes and re-create the build, then that is the final build. At some point, a build is "final". Something that happens after the "final" build means it WASN'T the final build. Um, derp? So, we now can agree that, at SOME point, the build is... finally final. Finally. In finitum. Done. Ship it. Go time. At THAT point, you can run the patch notes.
Really sick of the fanbois constantly defending ZoS' crappy software practices...
Hmm, you seem to be argumentative against anyone who presents an opinion different from your own. I think you might be in need of more coffee, or chocolate, or hugs.
While it is entirely possible that ZOS' methods of producing patch notes isn't optimal, telling them so on a forum thread is unlikely to get them to change their practices. Perhaps, instead, you should consider using a more direct approach to get your message to the appropriate channels.
I can, however, predict with some certainty that at some point during this thread a moderator will come in, edit some posts, and ask everyone to play nicely in the sandbox.Founder and Co-GM of The Psijic Order Guild (NA)
0.016%4 -
adean27✭✭✭I think your too hung up on the word finalizing. The reason you don't get patch notes first is because not all patches or fixes might be "accepted" by the system during update nit hasn't happened in a while, but there was a maintenance time early on when they had to scrap the whole patch process because of an error encountered. In your scenario of having them released ahead of time you would have people complaining about not getting something that they were promised. At that point they would have "lost" something.
They aren't typing the patch notes when the patch is being applied. They are waiting to see if the patch is finalized. Not the notes. On the live servers we always get the patch notes before the server is brought back online.
You are being highly critical for no reason of a process that needs to work in the way it does.
Nail -> Head.
I'm more worried about how angry the OP is in regards to this. It's not healthy to be so aggressive and angry about something so unimportant.
Please just enjoy the day and do not worry about a 2 hour difference on release of patch notes, it's not worth the effort. I for one will be going outside to enjoy the day, and for you other Canadians. Happy Thanksgiving!2 -
TehMagnus✭✭✭✭✭
✭✭onlinegamer1 wrote: »onlinegamer1 wrote: »First, 401 error is a client side HTTP access error, so you would NEVER see it in that format.
Second, not a single game company out there finalizes patch notes before implementation. Some release tentative notes ahead of time, but none finalize. ZOS does the same thing, they write tentative notes a couple of weeks ahead and modify them as needed.
Sometimes a server side patch will not be accepted as a certain aspect may not function on a live configuration, so they modify on the fly. Sometimes an item will be completed on patch day and implemented, so they add that too.
If You're in the industry you should know this, you would learn it first week as a QA.
1. It was a made up example, your point is stupid.
2. "All other companies suck at this process too" is not an argument.
3. You obviously didn't even read the OP, because having the patch note as part of the ticket means it doesn't matter what last minute changes you make, the final list of patch notes is generated from the final list of tickets.
Way to phone in your reply.
Well that escalated quickly...
1. It was to point out that your example is incorrect, which indicates a lack of knowledge in something you are claiming to know quite a bit about.
2. At no point did I indicate that any company "sucked", I indicated that an industry standard is to finalize patch notes once the process has begun. Something you would know working in the industry.
3. I think there seems to be some confusion on what "finalized" means. Just because something is scheduled to be added, does not mean at the last moment that it will in fact be added. As you indicated with your knowledge of the industry, you understand that a Live server configuration is completely different than an in-house system. On various occasions you can get sections of patches that come back corrupt when trying to update, or just do not function with the server side of things as intended, such as modifying functionality. Those things need to be removed, reconfigured, and added in a later patch.
4.
I hope you have a good day.
1. Example is absolutely correct. It was not "error 401", it was "Exception E401" a completely made up error. So, again, you're wrong.
2. Again, your argument is "all other game companies do it that way, so should ZoS". That is a logical fallacy called "Appeal to Tradition", and isn't a logical argument.
3. Again, you have to make a build. If you deploy a build and its broken, and you pull out one change/set of changes and re-create the build, then that is the final build. At some point, a build is "final". Something that happens after the "final" build means it WASN'T the final build. Um, derp? So, we now can agree that, at SOME point, the build is... finally final. Finally. In finitum. Done. Ship it. Go time. At THAT point, you can run the patch notes.
Really sick of the fanbois constantly defending ZoS' crappy software practices...
Gotta agree with OP, moreover, working myself in the industry on the QA part, I have the patch notes as soon as the dev team has installed the patch to UAT environment. Once we finish UAT testing the patch notes are virtually finalized and don't change that much unless we see something broken in Preproduction.
Before delivering to production(aka Live), someone from the business has to SIGN a document clearly stating what is going on production, so yes, if you're doing things right, you got patch notes BEFORE going to live and if the QA is done well, the margin for error between patch notes and what happens in production is minimal.
But you know, Fanboys...
3 -
Elsonso✭✭✭✭✭
✭✭✭✭✭onlinegamer1 wrote: »Many times, when people have asked ZoS for the patch notes, we were told, clearly and unambiguously, that they actually "finalize" the patch notes on the day of the patch. In other words, the actual patch notes document isn't final. In other words, they don't know what did or didn't make it into the patch, and they haven't come up with the "player-friendly" descriptions of each enhancement or bug fix.
Most of us in the industry know that a bug description can be very technical: "exception E401 in com.classes.player.inventory.junk when bag is full" isn't the kind of thing you want in a patch note, whereas "Fixed an issue where moving an item to junk when your bag was full didn't always work" is more understandable.
But, whenever a bug is being worked on by a Developer, or even if you wait until the bug goes to internal QA, it is at THAT time that you should already be filling in the "patch note" text in the ticket. That way, once that ticket passes QA and makes the final build, the patch notes are already built, and its not subjective or up to a human being to "make" the patch notes, you simply generate a document from the ticketing system, taking the "patch note" field of all tickets which are part of the final build.
This kind of process and automation is something a professional studio such as Zenimax should already have in place. And once again, it has nothing to do with wanting patch notes earlier. It has to do with making sure you KNOW what is being deployed in the patch, so as to minimize errors, false/incorrect patch notes, accidentally reverting previous fixes, and letting something go live that shouldn't.
I am quite certain that this process may work for some groups, but the path that the patch notes take from developer to forum is actually fairly clear and not at all unusual.
The patch notes are a press release. That is the first thing to keep in the front. They contain text that summarizes, in a general manner, the content of the patch that someone thinks is important for the subscribers to know. They may be written by professionals who know how to write press releases, or just someone who is good at writing this type of information up.
The patch notes press release is not a 1 for 1 list of all changes. Some changes do not get line items in the press release, and someone has to decide that. Some line items are actually a mashup of several related changes. Changes that were expected to be in the patch may get pulled late in the process. They may add high priority changes that were not in the initial patch content.
Thoughout all of this, a non-technical patch notes writer has to keep track of what line items need to be in the press release and what ones need to be removed.
So, yeah, they need to be finalized before being published. It is important to treat the patch notes as a press release, though.1 -
AnubisRe✭✭✭Patch notes are a technical document, not a press release and they should contain all changes made to a software since it is important for the customer to know what has been fixed, reworked and what parts of the software might be affected.1
-
onlinegamer1✭✭✭✭✭
✭Patch notes are a technical document, not a press release and they should contain all changes made to a software since it is important for the customer to know what has been fixed, reworked and what parts of the software might be affected.
While I agree with you mostly, I do think its ok to "flag" some tickets/fixes to be invisible/not included in the patch notes, specifically:
- internal fixes
- exploit fixes
Otherwise, yes, the idea that patch notes are a "press release" is nonsense.0 -
ZOS_GinaBrunoCommunity Manager
This is, for the most part, correct. The patch notes are generated, created and edited before the build and maintenance take place, but we do wait to see if any changes have failed before "finalizing" them. It also takes time to format them properly in the forums - the longer they are, the longer it takes. This is something we do need to do manually.I think your too hung up on the word finalizing. The reason you don't get patch notes first is because not all patches or fixes might be "accepted" by the system during update it hasn't happened in a while, but there was a maintenance time early on when they had to scrap the whole patch process because of an error encountered. In your scenario of having them released ahead of time you would have people complaining about not getting something that they were promised. At that point they would have "lost" something.
They aren't typing the patch notes when the patch is being applied. They are waiting to see if the patch is finalized. Not the notes. On the live servers we always get the patch notes before the server is brought back online.
You are being highly critical for no reason of a process that needs to work in the way it does.6 -
Zolron✭✭✭
[/quote]
This is, for the most part, correct. The patch notes are generated, created and edited before the build and maintenance take place, but we do wait to see if any changes have failed before "finalizing" them. It also takes time to format them properly in the forums - the longer they are, the longer it takes. This is something we do need to do manually.[/quote]
I am certainly no techie but why " wait to see if any changes have failed before finalizing them" ? Isn't that what the PTS is for? Plus from my understanding failure rate should be extremely low no ?Edited by Zolron on October 13, 2014 2:10PM0 -
ZOS_GinaBrunoCommunity ManagerMany times, changes are made but do not get published on the PTS first (today's build, for example).1
-
Maotti✭✭✭✭✭
✭ZOS_GinaBruno wrote: »Many times, changes are made but do not get published on the PTS first (today's build, for example).
I pray to Azura there won't be a "Sneknorist has been completely nerfed, no more grinding there possible".
Edited by Maotti on October 13, 2014 2:13PMPC EU0 -
Audigy✭✭✭✭✭
✭✭I honestly fail to see why this is such a big issue for people...
You will get the patch notes once they are online, some guys here act like the world would end if the notes come a few minutes too late.
Go out and take a drink, might help you to relax a bit
1 -
onlinegamer1✭✭✭✭✭
✭I honestly fail to see why this is such a big issue for people...
You will get the patch notes once they are online, some guys here act like the world would end if the notes come a few minutes too late.
Go out and take a drink, might help you to relax a bit
Congrats, you get 0 points for failing to actually read the OP.1 -
JessieColt✭✭✭✭onlinegamer1 wrote: »This isn't a thread whining about "gives us the patch notes!!1!one!"
This thread is about the fundamental problem of a software company (ZoS) applying an actual patch (server side and client side) BEFORE the patch notes are created.
Many times, when people have asked ZoS for the patch notes, we were told, clearly and unambiguously, that they actually "finalize" the patch notes on the day of the patch. In other words, the actual patch notes document isn't final. In other words, they don't know what did or didn't make it into the patch, and they haven't come up with the "player-friendly" descriptions of each enhancement or bug fix.
First of all, you have no idea if the patch notes have been created or not. Most likely they have been created since in most cases, that is what the QA team works from when they test the changes that were made.
Finalizing could mean, and most likely means, that they gather the list of what changes did made it into the release then they type up the document for posting to the forum.
As a gamer, and as a person who works in the game industry, I LIKE that they do this.
It makes it very easy to read through the patch notes that are posted to the forum.
It is nice to have the information regarding the releases in a format that makes it easy to read, where different fixes/changes are grouped together.
0 -
Dominoid✭✭✭✭✭
✭✭ZOS_GinaBruno wrote: »Many times, changes are made but do not get published on the PTS first (today's build, for example).
You tease. What is it . . . .what is it . . .0 -
ZOS_GinaBrunoCommunity ManagerFor what it's worth, we just published today's patch notes here: http://forums.elderscrollsonline.com/discussion/135634/patch-notes-v1-4-60
-
Audigy✭✭✭✭✭
✭✭ZOS_GinaBruno wrote: »For what it's worth, we just published today's patch notes here: http://forums.elderscrollsonline.com/discussion/135634/patch-notes-v1-4-6
For what its worth it, I think you are way to nice to people like the OP
You could add a wall of shame in the next ESO Live podcast featuring silly threads like this one
2 -
starkerealm✭✭✭✭✭
✭✭✭✭✭ZOS_GinaBruno wrote: »It also takes time to format them properly in the forums - the longer they are, the longer it takes. This is something we do need to do manually.
It honestly kind of surprises me that you'd be doing that in the forums editor. I know for my own work I tend to use Notepad (well, technically Notepad++) for cleaning up HTML before pushing it live.1 -
Soulshine✭✭✭✭✭
✭ZOS_GinaBruno wrote: »For what it's worth, we just published today's patch notes here: http://forums.elderscrollsonline.com/discussion/135634/patch-notes-v1-4-6
For what its worth it, I think you are way to nice to people like the OP
You could add a wall of shame in the next ESO Live podcast featuring silly threads like this one
Yeah now that is a brillant idea; ridicule a bunch of people already peeved off at you for something and expect improved communication as a result... good grief. No wonder...1 -
ZOS_GinaBrunoCommunity Manager
Well, it's a mixture of Notepad and forums, but that's neither here nor there.starkerealm wrote: »ZOS_GinaBruno wrote: »It also takes time to format them properly in the forums - the longer they are, the longer it takes. This is something we do need to do manually.
It honestly kind of surprises me that you'd be doing that in the forums editor. I know for my own work I tend to use Notepad (well, technically Notepad++) for cleaning up HTML before pushing it live. 0 -
onlinegamer1✭✭✭✭✭
✭ZOS_GinaBruno wrote: »
Well, it's a mixture of Notepad and forums, but that's neither here nor there.starkerealm wrote: »ZOS_GinaBruno wrote: »It also takes time to format them properly in the forums - the longer they are, the longer it takes. This is something we do need to do manually.
It honestly kind of surprises me that you'd be doing that in the forums editor. I know for my own work I tend to use Notepad (well, technically Notepad++) for cleaning up HTML before pushing it live.
@ZOS_GinaBruno, I highly recommend TextPad as a replacement for Notepad. https://www.textpad.com/1
