Stuart, So long as minor releases are not restricted to once a year, this may work. as it stands, we receive a new version, within a day or 2 we find bugs, and then have to wait 6 months for fixes.
And notwithstanding the point that there are bugs not fixed, years after discovery.
Obviously bentley do not publish the full bugs list, (which would be so useful to know) however it would be invaluable to at least have some kind of road map explaining and outlining the development path, and what is slated to be added/fixed in upcoming releases.
Microstation has progressed to major and a minor release cycle. One of the reasons for this was based on user feedback which told us that we can’t implement new features during quick release cycles and we prefer security and stability to become a priority. Bentley will release a major version of Microstation annually containing new features and security/stability improvements and minor releases primarily addressing security and stability. We feel this provides a good balance between those that expect continued new development and those that prioritize security and stability. Major and Minor releases are spoken about in here. https://www.youtube.com/watch?v=rpP4h3kGxas and read here. https://www.bentley.com/support/bentley-lifecycle-policy/.
But the list of bugs is so long, and some are years old Stuart. Bentley must prioritise fixing all bugs from previous versions, before releasing an update, that way the only bugs that should be present relate to the current version, and not long standing historical bugs.
If a bug is found, it should be fixed in the next release.
Bug fixes will addressed side by side with new features. This is to satisfy both those who expect bug fix priorities and those who expect new features.
Stuart,
So long as minor releases are not restricted to once a year, this may work. as it stands, we receive a new version, within a day or 2 we find bugs, and then have to wait 6 months for fixes.
And notwithstanding the point that there are bugs not fixed, years after discovery.
Obviously bentley do not publish the full bugs list, (which would be so useful to know) however it would be invaluable to at least have some kind of road map explaining and outlining the development path, and what is slated to be added/fixed in upcoming releases.
Thanks for the feedback.
Microstation has progressed to major and a minor release cycle. One of the reasons for this was based on user feedback which told us that we can’t implement new features during quick release cycles and we prefer security and stability to become a priority. Bentley will release a major version of Microstation annually containing new features and security/stability improvements and minor releases primarily addressing security and stability. We feel this provides a good balance between those that expect continued new development and those that prioritize security and stability. Major and Minor releases are spoken about in here. https://www.youtube.com/watch?v=rpP4h3kGxas and read here. https://www.bentley.com/support/bentley-lifecycle-policy/.
Hi Stuart.
Understand, but some of the BUGs are huge concerns for the users. one that I have logged over and over is SPEED of CE v V8i.
But the list of bugs is so long, and some are years old Stuart. Bentley must prioritise fixing all bugs from previous versions, before releasing an update, that way the only bugs that should be present relate to the current version, and not long standing historical bugs.
If a bug is found, it should be fixed in the next release.
Bug fixes will addressed side by side with new features. This is to satisfy both those who expect bug fix priorities and those who expect new features.