Upgrade StorageGitHub question
My IT dept doesn't like to update for every version so I'm looking for a way to optimize my update requests and avoid updating just before a new version comes out if possible. Any suggestions?
I know Zotero doesn't make any statements about new version releases, but can the GitHub log help users to make inferences at all? For example, when looking at the GitHub log (https://github.com/zotero/zotero/commits/), there is a commit from July 23 entitled "Update Version". Viewing commit details, the version listed in the green + line is 6.0.12, while the download for the website is .10 and the latest in the documentation is .11. So, does the GitHub commit imply that update 6.0.12 may be coming soon? Does it mean .12 is just being started? Any insight regarding what might be inferred (recognizing there are no promises or absolutes), would be most appreciated.
Thanks.
I know Zotero doesn't make any statements about new version releases, but can the GitHub log help users to make inferences at all? For example, when looking at the GitHub log (https://github.com/zotero/zotero/commits/), there is a commit from July 23 entitled "Update Version". Viewing commit details, the version listed in the green + line is 6.0.12, while the download for the website is .10 and the latest in the documentation is .11. So, does the GitHub commit imply that update 6.0.12 may be coming soon? Does it mean .12 is just being started? Any insight regarding what might be inferred (recognizing there are no promises or absolutes), would be most appreciated.
Thanks.
That's the thing to look at. It shows you that 6.0.10 was released on July 18 and 6.0.11 was just a fix for macOS the next day. We usually bump the version ("Update version" commits) before pushing out the next beta, so you'll usually see that a day or two after the most recent release.
There's no fixed release schedule or cadence, so the safest option would just be to request an update from your IT department shortly after a new version comes out that has something you want or has an important bug fix. You'd probably want to wait a few days to make sure there wasn't a major regression that required a follow-up release soon after (and you might get an idea from GitHub or forum threads here whether we were tracking or had fixed such a bug). But Zotero these days has an extensive test suite, so immediate bug-fix releases for minor releases aren't that common. (Something like the initial Zotero 6 releases in March were obviously an exception.)
There's an RSS feed for the wiki that include changelog changes, but I don't think it's possible to limit it to a specific page. You could use some external tool for that if you want to be notified when it changed, though.