ehrezDo you have a pest practice for the best process to suspend or stop a update that has been published already?
For example, a new version is published on monday, this new version introduces a bug that cannot be fixed right away. The update is suspended on tuesday until a fix can be developed.
Thank you.
Do you have a pest practice for the best process to suspend or stop a update that has been published already?
Select the last working "built to" version in wyBuild, click Build Updates, then re-upload the files to your servers.
That's the best practice right now.
ehrezQuick question, after publishing the last working "built to" version to the servers, will anyone who installed the broken patch go back to the one just published?
Example: We publish version 1.2 which introduces a bug; version 1.1 is republished to the servers following the procedure you mentioned; the people who updated to 1.2 revert back ro 1.1?
We want those users who updated to revert back to the last working version and those who hadn't upgraded yet to stop getting the "new version available" prompt.
Thank you in advance.
We're adding the ability to mark updates as "rotten" in wyBuild 2.7. In the way to do this is to push out a "new" version that's just the last working version. That is, let's say you have version 1.0, 1.1, and 1.2. Then you find out 1.2 has a huge bug that you missed and it will take a week to fix. Create "1.2.1" in wyBuild, then add the "1.1" files to this version, rebuild your updates, upload them to your server.
All users will be updated to "1.2.1" (which is really 1.1).
Does that make sense?
