Suggestion: Indicate if the current version is a Release Candidate

NichtnurBibelleser

It seems that I made the same mistake re: Version Number as someone else.

Therefore I would request to indicate in a clearer way if the current version is a Release Candidate.

(@Harry Hahne I appreciate your move and borrowed it to create a poll hoping that it will be more visible)

Find more posts tagged with

Not now

Desktop App

Status: Not Now

Comments

Graham Criddle

As per Bradley's comment in the post you linked to, the Logos team need to ensure that the RC releases are identical to stable releases (I guess apart from build number).

What sort of clearer indication would you like to see that satisfies this constraint?

NichtnurBibelleser

Sorry, @Graham Criddle , I still don't get it. The info found at https://community.logos.com/kb/articles/2919-logos-46-0 talks about RC or Stable?

Graham Criddle

The information in the link you provided relates to build 46.0.319 and is in the area of release notes used for stable releases. So all the indications are that these are the release notes for the 46.0 stable version that should ship sometime today.

Whereas the release notes here refer to build 46.0.312 and relate to RC1 (and these are from the beta release notes area)

In general, irrespective of when release notes are posted it's best to wait for the announcement in the forums for the release having shipped.

Does that help at all?

Bradley Grainger (Logos)

I guess apart from build number

No; if RC 1 is shipped as the "RTM" release, the build number will be exactly the same. (The best way to ensure that no regressions are accidentally introduced is to ship the exact same code that's already been in RC testing.)

Of course, if a RC 2 is produced (to fix a bug) the build number will change.

NichtnurBibelleser

Thanks to everybody who helped - I think I understand now. Sorry for the confusion created.

Graham Criddle

No; if RC 1 is shipped as the "RTM" release, the build number will be exactly the same.

Of course, sorry @Bradley Grainger (Logos)