para-CAD Posted 17 hours ago Share Posted 17 hours ago Ball park time frame would be nice. Thanks. Link to comment Share on other sites More sharing options...
Mark3D Posted 15 hours ago Share Posted 15 hours ago Another post said early July Link to comment Share on other sites More sharing options...
para-CAD Posted 13 hours ago Author Share Posted 13 hours ago Public Beta? So when is Release Candidate? When I started with X7, it seemed that new versions came out in FEB/MAR timeframe. I've heard online debates where people make the claim that if you're paying a subscription to something, then the updates should be incremental and ongoing throughout the year. as opposed to when you own the software and you have to be enticed into paying for a yearly upgrade or an SSA. 1 Link to comment Share on other sites More sharing options...
Smn842 Posted 8 hours ago Share Posted 8 hours ago 4 hours ago, para-CAD said: I've heard online debates where people make the claim that if you're paying a subscription to something, then the updates should be incremental and ongoing throughout the year. as opposed to when you own the software and you have to be enticed into paying for a yearly upgrade or an SSA. I've worked in software all my career and in general yes subscription does reduce the need for annual releases and shifts the balance of needing upgrade selling features in each major release. There is a limitation for desktop software that some changes affect the database schema and for Chief this could require a change to plan file format or other general program storage. This means a software company doesn't want to be making such schema changes too often as it would be a support nightmare and confusing for customers. Customers would need to ensure all their or their teams installs updated in sync as is done for major releases now, and Chief Support would need to have all the versions at hand for testing customer data. That said there are still changes that do not need schema changes, and in the software I've worked on we often had 2 and sometimes 3 schema changes a year (marked by a new point releases so v4.1. 4.2 etc) and that gave us a good balance of getting features that needed schema changes released without overly complicating things. Including the non schema breaking changes we often released 4+ times per year not including important bug patch fixes. That didn't limit major changes as in parallel we would work on those longer projects that were in development for 12 to 18 months before finally being merged into the next release. Link to comment Share on other sites More sharing options...
para-CAD Posted 46 minutes ago Author Share Posted 46 minutes ago Thank you for sharing your experience and educating me a little bit deeper into the software design process. It’s much easier for me to be patient when I understand the depth of effort that is required in upgrading a software app or platform. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now