Lower build numbers in newer releases (NERD ALERT)

Plex Media Server
41

random

42

SHA-1 is my favorite random number generator :stuck_out_tongue: except for ChaCha20

(Side-note for everybody, please include the commit hash when posting version numbers [e.g. version an issue is happening on, last known good version prior to a regression etc.], it makes our lives dramatically easier, which means your issues get investigated quicker!)

43

So, has there been a case where a hotfix (or whatever) was applied to a release and only the commit ID changed, but not the build number? That would be even more confusing (and would likely not trigger any update prompt).

44

@Ridley - FYI, the forum post and in-app alert are for 1.29.1.6260, but the version available to download from https://www.plex.tv/media-server-downloads/ is still 1.29.1.6241. I assume this is just things catching up with each other?

FWIW, hashes aren’t listed on the Forum announcements post, and they aren’t listed in PMS itself, either in the in-app Update notification or Settings → General.

image

45

It was edited from 6241 earlier


46

Nope, that’s not possible; a build number refers to a specific build, produced at a specific time, from a specific commit.

47

OK, one more thing then, and forgive me if this was already answered (it probably was). If a fix was applied in let’s say version 1.34.2.7445, and later version 1.34.3.7442 is released, does that mean that fix is in version 1.34.3.7442 or not?

48

Not automatically, but generally if we backport a change to an older release branch, it’s either already in any newer release branches, or is backported to them at around the same time.

1 Like
49

The latest package listed on the Announcements section should be the current release with all previous fixes merged in from earlier releases.

1.29.1.xxxx has all the fixes from 1.29.0.xxxx +some. Otherwise it’s confusing for the people downloading the software.

xxxx doesn’t matter unless it’s a subsequent release of the same eg: 1.29.0.

50

No offense, but I don’t think you’ve read the whole thread. What you just stated is not necessarily the case, as previously established. Let’s leave it at that.

51

No offence but I’m pretty sure I’m stating how it should be. Key word is “should be” in the last post.

Patch .1 is going to have all the fixes that patch .0 has plus any other fixes. Unless the release notes state otherwise then it’s a complete cluster ■■■■ for the people downloading and using the software. PERIOD.

Ever hear of the term regression? Why on earth would any software company release a fix and then in the subsequent version not include it? Unless it is specifically dropped for a reason it makes no sense.

52

I genuinely love that phrase because it can convey nearly-opposite meanings.

  • “Should” can mean “I believe that it is currently so.”
  • “Should” can also mean “It would be better if this was the case.”
2 Likes
53

Another example today of a build being published (6313) where no release notes are included saying what changed between it and the previous build (6276) :frowning:

Screenshot from 2022-10-19 14-39-55
Screenshot from 2022-10-19 14-39-55756×450 23.8 KB

2 Likes
54

@anon5074910 nailed it. I came to ask the same question. The 6276 beta is running well for me, but now the 6313 changes that are in the public release are a mystery.

55

I see its been edited to add the changes – thanks!

56

Well they added changes, but removed the ‘public’ version 1.29.1.6313 and replaced it with a beta version 1.29.1.6316 and yet the (plex pass version) on the downloads page is only offering 1.29.1.6276

57

I was offered the beta 6313 update, but when I clicked on the download button nothing happened and now it says 6276 is the most current. Weird goings on.

58

I’m now getting offered 6316 in the beta channel, and a file with the correct version name does download (for Linux), but I’m waiting this one out for a while.

59

So, here we go again:

1.30.0.6359-1185e28d9, October 31, 2022

1.29.2.6364-6d72b0cf6, November 1, 2022

Anyway, I don’t want to get into the whole “build” discussion again, but if someone could expand on what this means:

  • (PlexMatch) Add support for pattern matching (#13899)

Also, what is this fix about, since this has always worked:

  • (Scheduled Tasks) Perform periodic metadata refreshes on TV shows too (#13920)
1 Like
60

To answer my own question:

image
image325×122 8.35 KB

Refreshing “Shows” is new/working now, when before it would only do “Seasons”. Thanks for that!

1 Like