Support Suite
User Login
How do we do EIOBoard Releases and Naming Conventions
Posted by Savance on 17 August 2010 07:28 PM
|
|||||||||||||||||||||||||||||||
We have an automated e-mail for Customer-Hosted and EIOBoard-hosted that are different. Each time a new customer signs up for a trial or we release a new version, they get an e-mail with links for a specific release. All links will be downloaded from the corresponding release's download directory on our server, http://www.eioboard.com/downloads/releases/X.X.X/filename. The "X.X.X" is the full version number. The filename is typically EIOBoard{Interface}X.exe where X=version number and Interface = App, Outlook, etc. So EIOBoardApp7143.exe would be the v7.1.43 release (full path would be http://www.eioboard.com/downloads/releases/7.1.43/EIOBoardApp7143.exe). As we have minor patches/revisions that we’re confident are ready for general release, we’ll update the general release file. So some days, the link might be downloading 7.1.43 and a few days later, it might be downloading version 7.1.44. The latest official release can always be found at http://www.eioboard.com/downloads/latest/filename where the filename like before is typically EIOBoard{Interface}.exe but without a version number. (For example to get the latest EIOBoard Application the link is http://www.eioboard.com/downloads/latest/EIOBoardApp.exe) We always have the hard reference to the specific release available if a customer needs a certain release to match what they’ve deployed in the past. As a good rule of thumb, once you get your e-mail to download your version, download the server installer (if customer-hosted) and all the interfaces you might use into a directory and store it on your EIOBoard server or on a file server. This will ensure you keep the same version to deploy to your users and do not deploy one version during deployment and a newer version a few weeks later. Here is a cross reference to our version/download conventions: Or
| |||||||||||||||||||||||||||||||
|