Release versioning broken docker bots

[PaulMcG1970 0]

Hi,

up until the latest version all beta releases have the third version digit as 0 for example:

4.9.0.43

4.9.0.59

4.9.0.60

 

And all release versions had a numeric value as the third digit:

4.8.6.0

4.8.7.0

4.8.8.0

etc... to

4.8.11.0

 

5 days ago the latest beta version was released as

4.9.1.0

 

This has broken docker bots which compile new distributions based on release versions.  It is not possible for them to check for the text "-beta" on the end of the version so they cannot distinguish between 4.9.1.0 and 4.9.1.0-beta

[Abobader 3464]

Hello PaulMcG1970,

** This is an auto reply **

Please wait for someone from staff support or our members to reply to you.

It's recommended to provide more info, as it explain in this thread:

Thank you.

Emby Team

[revengineer 142]

Looks like we are starting over the count to 60 rather than having a release. 

[Luke 42078]

OK that's unfortunate, but it shouldn't be too long until there is an actual 4.9 stable release. Thanks.

[PaulMcG1970 0]

Hopefully the release version is greater than 4.9.1.0

[OneHungryPoboy 0]

8 hours ago, Luke said:

OK that's unfortunate, but it shouldn't be too long until there is an actual 4.9 stable release. Thanks.

Luke, will the versioning mentioned in the first post still be used moving forward or is that an unreliable method to determine release vs beta?

[Luke 42078]

22 hours ago, OneHungryPoboy said:

Luke, will the versioning mentioned in the first post still be used moving forward or is that an unreliable method to determine release vs beta?

I prefer to have the stable releases end in a 0 but I wouldn't necessarily promise that.