NOTICE: Registration may require manual admin activation. After registering visit https://bitsum.com/contact/ to request account activation.
Started by Montgomery, September 06, 2015, 11:53:32 AM
Quote from: edkiefer on September 06, 2015, 01:20:09 PMI am confused , if you do manual install , where does it say 184.108.40.206 is not available ?DL from this link an install.https://bitsum.com/forum/index.php/topic,5016.msg19396.html#new
Quote from: edkiefer on September 06, 2015, 02:33:56 PMOk, I see , you are still using auto-updater , just you are triggering it manually .The issue is probably how builds are ID# , Jeremy I am sure can look into fixing it up hopefully .I am on beta so I didn't run into this issue .
Quote from: Jeremy Collake on September 06, 2015, 06:09:58 PMHere's the deal:220.127.116.11 from 18.104.22.168 only has changes to the installer and a couple Italian strings. It was released a day after 22.214.171.124, and I saw no reason to bother any user of 126.96.36.199 with it, since the only changes are so minor and affect more the installer than anything else. There will be a new final pushed out within a week anyway, so I'm just limiting how much people are bothered with updates. It was quite intentional.
Quote from: Montgomery on September 07, 2015, 05:01:42 PMOK! If I could have guessed I wouldn't have made a post out of it.
Quote from: edkiefer on September 07, 2015, 05:35:28 PMDon't worry about it , you did good reporting what you see .It could of had a different outcome
Quote from: Jeremy Collake on September 07, 2015, 05:35:48 PMNo problem. I knew better than to do this, and it turns out the installer change I made wasn't even important. Sometimes I'll refresh the current build without changing the version number. You know, a few new strings, or other minor things. However, in this case, I thought I'd go to .1 to officially demarcate a new build. All in all, poor release management on my side. Apologies for this.