Does Plex use semantic versioning for build numbers? If not, what is used?
Would it be fair to assume that last patch on the previous minor release (1.24.5.5173) is the most stable recent build?
Does Plex maintain multiple release branches, for example we are currently seeing patches for 1.25.x would we ever see a release for 1.24.x or is it a single release branch?
What can we expect for backwards compatibility in relation to Plex’s API’s and client apps when connecting to Plex Media Server?
We try, but sometimes new stuff slips in a patch version 
Nope, always go with the latest Non Plex Pass build!
PP Builds are to be considered betas, that might get promoted to releases
Nope, it’s a one way train
Before a release, we do test our officially supported clients, but it’s hard, since when on like Samsung, where the same client runs on multiple models, there might sometimes be difference within the vendor models.
And we simply can’t buy a test TV for every model Samsung makes
Same goes for other vendors
We also ONLY test PMS against latest version of our clients
Regarding API, we do try and be backwards compatible, but since we never released the Rest API for PMS to the public, 3rd. Party did found out via like sniffing on the wire, log debugging etc. so sometimes it do happens that we break 3rd. Party unwillingly.
Historically, we have then tried our best, when raised, if possible to fix that though, since we are a nice company, and want the best for everybody, including 3rd Party clients
So when I look at the release notes for Plex Media Server 1.25.9.5721 compared to the next release of 1.26.0.5715 I am having trouble following why the minor number was increased when it just looks like a patch for the previous release. Please enlighten us 
I have also been noticing a divergence in the Plex Media Server (Web) vs what we see at app.plex.tv, what is the roadmap around this?
When you look at the rev number, you’ll see that 1.25 was commited later than the 1.26 version, and that can happen when different branches are handled.
Not talked to the eng. that made the build, but guess the choice was between 1.25.10 or 1.26.0 
There’s no magic behind it, simply humans
Your previous reply indicated that it was a single release branch, did that change as now your indicating multiple release branches indeed do exist.
In searching released Plex Media Server build numbers it appears that version patch number of the semantic version is never greater then 9 and when that number is reached as it was in this case the next build gets the minor number incremented for visual appearances?
Are you also saying that version 1.25.9.5721 is newer than 1.26.0.5715?
Oh…I never mentioned a specific release branch!
We have no rule for that, AFAIK, so would guess you just spotted a pattern that’s simply a coincidence
No!
Reason 1.25 has a higher rev number is because it was build after 1.26, but 1.26 is the newest
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
