In my case, In MacUpdater Zoom is shown with build numbers in brackets, for example, 5.9.3 (4239), This is indeed a big limitation of apple versioning system > 3) uses a lower number for beta versions than production versions for the same release version (e.g., 5.0.97-beta.1 I don't love the idea of showing long, incorrect version numbers for production releases. (MacUpdater might find another way to version Zotero Beta perhaps) I am in contact with one of the MacUpdater developers through support email, I forwarded him this conversation and asked him if he has something to add
Whats macupdater update#
I use it most often to show me if there are any updates, I update through Zotero's own thank you for your swift reply I am sorry for the confusion, indeed it was MacUpdater App (by corecode), for the release version strings (which is legible enough that I'm still comfortable with it).) (If we want these numbers to always be accurate, we'd also either need to stop doing hotfix builds like 5.0.97.1, which we've used for various purposes previously, or use something like, , etc. Unless anyone has other insight on this, I'll go ahead and make that change for an upcoming beta. That's probably our best option, and it's hard to think of how using different scheme for different channels would really could a problem. So that leaves sacrificing (3), which would let us use 5.0.97 for the production release and something like 058 for 5.0.97-beta.58.
We could sacrifice (4) and use some arbitrary scheme where the channel was embedded in a longer number (e.g., 058 for 5.0.97-beta.58, 000 for 5.0.97), but I don't love the idea of showing long, incorrect version numbers for production releases.
Whats macupdater manual#
It's not clear to me if MacUpdater was actually doing something with that string (in which case it would've had to have been parsing invalid version strings) or just displaying it to you for manual action, but using an invalid string seems like a bad idea regardless. We could sacrifice (1) and keep doing what we were doing before, with an invalid version string. We were already using "5.0.97" for the beta for CFBundleVersion, and we recently changed CFBundleShortVersionString to do the same to stop using an invalid number (though it's possible that a technically invalid number is better than a non-unique number).īasically, though, there's no option here that 1) uses valid macOS version strings, 2) encodes the release channel, 3) uses a lower number for beta versions than production versions for the same release version (e.g., 5.0.97-beta.1 < 5.0.97), and 4) shows the actual version number for production builds. , which can't describe our beta versions. Zotero 5.0.97-beta.58+44b6cd052, © 2006-2018 Contributorsīoth CFBundleShortVersionString and CFBundleVersion are supposed to be just. Apple's versioning scheme for app numbers is really limited, with no ability to specify beta versions, and we were previously putting an invalid version string in one of the available fields: This wasn't a mistake - we just don't have a great option here.
0 kommentar(er)
