Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Wed, 15 May 2024 08:10:22 +0000
Suggestion in Pre-release Numbering
View Count: 1052
| [2017-10-23 11:30:00] |
| Xfanman1 - Posts: 320 |
|
It seems that Pre-release versions of SC often get incrementental updates before they are rolled into the next main release or another whole number Pre-release version. Is it possible to append the whole number in a Pre-release with an alpha character so we can see if we have in fact gotten the most recent changes? As an example, Pre-release 1626, 1626a, 1626b, 1627 and so on? I often see comments made to people awaiting changes or fixes (myself included) to download the latest Pre-release because you just updated the code even though I see that pre-release number may not have changed for days. This isn’t critical of course but just a suggestion (if possible) to help clear up some minor confusion among the user base. Thanks much....Scott Date Time Of Last Edit: 2017-10-23 11:41:14
|
| [2017-10-23 17:15:26] |
| |
|
What we really need to do is always increment the version number even with small changes. Sometimes we just want to avoid that. But we should do that.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2017-10-23 17:21:20] |
| Xfanman1 - Posts: 320 |
|
What we really need to do is always increment the version number even with small changes. Sometimes we just want to avoid that. But we should do that.
That certainly works too, I just thought you'd still be able to use whole numbers for your regular version changes and append the PreRelease's until you were ready for a regular release update. |
To post a message in this thread, you need to log in with your Sierra Chart account: