10-23-2014, 12:32 PM
(10-23-2014, 11:56 AM)doveman link Wrote: [ -> ]Sorry but you did say we should update because people were manually updating anyway and it would be harder to make them rollback, not because it's been shown to be stable, so I figured there's not much point serving a specific version to PwS users if we're going to update anyway just because non-PwS users have.Ok, I see I created a confusion. Let me explain what I think is the best policy: I think we should update only once a version proves to be functional and stable. A version can be proved stable fast by reviewieng test results of testers on the relevant thread. Our mistake was to update to 0.9.3 on a game night, before it proved stable.
(10-23-2014, 11:56 AM)doveman link Wrote: [ -> ]Anyway, people can select v0.9.6 on PwS and it won't update until they manually select a different version, so we can tell them to do that and not change it until we say to in the PwS thread. That seems easier as it doesn't rely on me updating the profile every time a new version is released, which might be a problem if I'm away on holiday or something. We can check tonight that everyone using PwS knows to do this and is subscribed to the PwS thread (and again on Sunday for anyone who's not around tonight), so I don't think it should be a problem.
As long as we can prevent auto-update the second a new version is out, it's great. Sorry, I'm not very familiar with how PwS works.
