Or is it going to trash my install like the one built a few days ago?
And why is it a good idea to rebuild a release under the same label even if the code is different? I think it is ok to add a super super minor to it. Or maybe mix in some semantic versioning.
Is the latest 2.2.2 ready to go?
Re: Is the latest 2.2.2 ready to go?
This one and some other things were fixed.
I do agree with you about re-using version numbers.
Don't know if it is safe to use. I still get stange behaviour with Login/Logout. In Firefox the Login screens are no longer automatically filled with uname/passw.
At first start-up it bypasses login and says there are no devices. The only tool is logout. After I have done that, I do get the login screen. After manually filling the fields I do get everything working fine, until I quit FF.
I do agree with you about re-using version numbers.
Don't know if it is safe to use. I still get stange behaviour with Login/Logout. In Firefox the Login screens are no longer automatically filled with uname/passw.
At first start-up it bypasses login and says there are no devices. The only tool is logout. After I have done that, I do get the login screen. After manually filling the fields I do get everything working fine, until I quit FF.
Re: Is the latest 2.2.2 ready to go?
Is there a place to get notifications about new releases. I thought they were announced in the forums (officially), or is the only way to track the issues on github?
I've had the same issues regarding the login screen...
I've had the same issues regarding the login screen...
Re: Is the latest 2.2.2 ready to go?
No they don't notify. I really have no idea why they don't