Skip version number for next CbB release...

Author
Post
Essentials Only Full Version
tecknot
Max Output Level: -75 dBFS
  • Total Posts : 766
  • Joined: 2004/10/31 17:09:29
  • Status: offline
2018/11/07 14:14:35 (permalink)

Skip version number for next CbB release...

No knock on Cakewalk or BandLab, but should BL just skip naming the next release of CbB 2018.10 and just go with 2018.11?  After all, I would rather receive a new version closer to the beginning of the month rather than at the end (or after the month corresponding to the version name/number).
 
Kind regards,
 
tecknot
#1

2 Replies Related Threads
    cowboydan
    Max Output Level: -72 dBFS
    • Total Posts : 908
    • Joined: 2012/01/13 06:10:21
    • Location: Asperen, Netherlands
    • Status: offline
    Re: Skip version number for next CbB release... 2018/11/07 14:50:38 (permalink)
    If the update doesn´t come out until the end of November it wouldn´t make a difference.
    #2
    bitflipper
    01100010 01101001 01110100 01100110 01101100 01101
    • Total Posts : 26036
    • Joined: 2006/09/17 11:23:23
    • Location: Everett, WA USA
    • Status: offline
    Re: Skip version number for next CbB release... 2018/11/07 15:59:18 (permalink)
    That number is just a minor version designation. The version of Chrome I'm using today is 70.0.3538.77. Those numbers just reflect a historical sequence, nothing else. If there is a Cakewalk release every month, then the minor version number will just happen to match up to the month of release.
     
    But BL is not on a predetermined release schedule. That's a good thing. It means you get the release when it's ready, which is what we all want. They just like to get bug fixes out as soon as possible, which is why releases have been coming along at a (mostly) steady rate.


    All else is in doubt, so this is the truth I cling to. 

    My Stuff
    #3
    Jump to:
    © 2024 APG vNext Commercial Version 5.1