-
Background
Our QA team thoroughly tests our products before each release, but sometimes bugs can still occur. We review all reported bugs, try to reproduce them, and prioritize them based on their impact. Each release includes several bug fixes found by both our team and clients.
-
What is a Bug?
A bug is a flaw that causes incorrect or unexpected behavior. If a feature doesn’t work as described in our documentation, it’s a bug. Missing features for your specific environment are considered feature requests, not bugs.
-
Handling Bugs
- Report: Bugs are reported through Support, Partners, Sales, or our Community.
- Diagnose: Our Support team tries to reproduce the issue.
- Review: The QA team provides technical background.
- Prioritize: The Product Owner sets a priority for the bug.
- Fix: Developers work on the fix, which is then tested by QA.
-
Release: If tests pass, the fix is included in an upcoming release.
This article illustrates the process graphically and explains it in detail.
- Bug Severity Levels
-
- Critical: Crashes, data loss, major security risks.
- High: Persistent issues, performance problems, failed upgrades.
- Medium: Non-critical issues with workarounds.
-
Low: Minor styling or spelling errors.
-
Releases
We regularly release new features and improvements, including bug fixes. Release notes are provided with each release. SaaS customers may receive fixes sooner than those using on-premises installations.
To access a bug fix, you will need to upgrade to the latest version of the software containing the bug fix you are interested in. VertiGIS does not provide hotfix releases to address bugs on previously released versions of software.
We would also like to refer to our VertiGIS Product Backlog Policy.
-
Software Versioning
We use semantic versioning:- Major: Significant changes and new features.
- Minor: New features and enhancements without breaking changes.
-
Maintenance: Bug fixes only.
-
Closing Remarks
We update our policies based on customer feedback. For more information about a bug you reported, please contact our Support.
Comments
0 comments
Article is closed for comments.