- Joined
- Feb 27, 2003
- Messages
- 8,509
Hello!
The team has been busy as always, and we're pleased to announce the release candidate for 1.62.5:
Version: 1.62.5 RC1
This is mainly a minor bugfix release with all changes listed here:
The most notable feature would be the use of new release channels, which can be set in the Admin Licensing/Updates page:
The default for everyone is "current" which matches the version listed on our website.
We've added "stable" will will trail behind for an amount of time which we deem sufficient to confirm the release has gone smoothly (guessing a few weeks).
There's also an "alpha" channel (pre-release in it's previous definition for quick fixes and bleeding edge new features), and "beta" channel, referring to referring to locked release candidates (aka: this release). If anyone had a hard-coded pre-release download script path (alpha), note it's different than before (beta takes that path so it will be updated far less often).
To try out these binaries, please grab them from the pre-release area (beta channel):
And from there, you can change your channel to beta in:
Admin Level » Licenses/Updates
which will always let you know when there's a new version in that channel (hooray for automation).
The SHA commit hashes are used to control "latest or not" state for alpha/beta.
The "stable" branch is version number specific.
Anyone on alpha/beta channels would be recommended to keep things to the latest to ensure any new bugs are fixed more quickly (up to you)
Note: the getDA.sh alpha only works for alpha once you get this new beta pack.
Should you run into any issues, please let us know in the forum below, to duplicates in the ticket system.
Thanks!
John
The team has been busy as always, and we're pleased to announce the release candidate for 1.62.5:
Version: 1.62.5 RC1
This is mainly a minor bugfix release with all changes listed here:
The most notable feature would be the use of new release channels, which can be set in the Admin Licensing/Updates page:
The default for everyone is "current" which matches the version listed on our website.
We've added "stable" will will trail behind for an amount of time which we deem sufficient to confirm the release has gone smoothly (guessing a few weeks).
There's also an "alpha" channel (pre-release in it's previous definition for quick fixes and bleeding edge new features), and "beta" channel, referring to referring to locked release candidates (aka: this release). If anyone had a hard-coded pre-release download script path (alpha), note it's different than before (beta takes that path so it will be updated far less often).
To try out these binaries, please grab them from the pre-release area (beta channel):
And from there, you can change your channel to beta in:
Admin Level » Licenses/Updates
which will always let you know when there's a new version in that channel (hooray for automation).
The SHA commit hashes are used to control "latest or not" state for alpha/beta.
The "stable" branch is version number specific.
Anyone on alpha/beta channels would be recommended to keep things to the latest to ensure any new bugs are fixed more quickly (up to you)
Note: the getDA.sh alpha only works for alpha once you get this new beta pack.
Should you run into any issues, please let us know in the forum below, to duplicates in the ticket system.
Thanks!
John