You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Starting from August 2023, we will be implementing changes to our approach for version support and versioning. This post outlines the new strategies and processes that will be in place to ensure efficient release planning, seamless version support, and streamlined versioning procedures.
Release Planning
Efficient release planning is crucial for delivering quality software to our users while meeting business objectives. Our updated release planning process will focus on the following key aspects:
Clear Objectives: Each release will be driven by well-defined objectives, aligning with the needs of our users and the goals of the organization.
Prioritization: Features and improvements will be prioritized based on their impact and importance, allowing us to address critical issues and provide meaningful enhancements with each release.
Flexible Scheduling: We will adopt a flexible scheduling approach that accommodates changes in priorities and unexpected developments, ensuring that our releases remain adaptive to evolving requirements.
Version Support
To ensure effective version support, we are implementing a revised strategy:
Defined Support Period: Each software version will be supported for a predefined period outlined in our calendar. This duration will ensure that users receive timely bug fixes, security updates, and compatibility adjustments.
Version Transition: With the release of a new version, support for the previous version will be maintained for 12 months. This will provide users with a transition period to migrate to the latest version while still receiving essential support for their existing installations.
Our revised versioning approach aims to provide clarity and consistency:
Semantic Versioning: We will adopt Semantic Versioning (SemVer) for our software releases. The version number will consist of three segments: MAJOR.MINOR.PATCH. Each segment will have a specific meaning:
MAJOR version: Significant changes and backward-incompatible updates.
MINOR version: New features and backward-compatible enhancements.
PATCH version: Bug fixes and minor improvements that maintain compatibility.
Clear Communication: Version numbers will be accompanied by release notes that succinctly outline the changes in each release. This will facilitate a better understanding of what users can expect from each version.
Versioning Strategy
In our transition towards a more streamlined versioning process, we are discontinuing the use of labels like "godot4-v1.0.0" and "godot3-v1.3.3." Instead, we are introducing a more organized and standardized versioning approach.
New Versioning Format
Moving forward, each release will be identified using the format vMAJOR.MINOR.PATCH. This format provides a clear indication of the significance and content of each version.
Release Notes Enhancement
To enhance transparency and clarity, every version's release notes header will now prominently display the USED AND TESTED version of Godot. This ensures users are informed about the specific version of Godot that was employed during testing and development.
Example:
v1.3.4
Version used and tested: Godot 3.5.2
v2.0.0
Version used and tested: Godot 4.1.1
v3.0.0
Version used and tested: Godot 4.1.1
Handling Major Changes
In cases of significant changes, such as issue #82 (a MAJOR change), when multiple versions of Godot are still under support (e.g., Godot 3 and 4), it's important to note that only the most recent version of Godot (in this example, Godot 4) will support the newest features.
Disclaimer
Please note that our software is distributed under the MIT license, THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND.
Additionally, these rules and strategies may vary based on workforce availability or other related factors. We appreciate your understanding of the dynamic nature of software development and its associated considerations.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Introduction
Starting from August 2023, we will be implementing changes to our approach for version support and versioning. This post outlines the new strategies and processes that will be in place to ensure efficient release planning, seamless version support, and streamlined versioning procedures.
Release Planning
Efficient release planning is crucial for delivering quality software to our users while meeting business objectives. Our updated release planning process will focus on the following key aspects:
Clear Objectives: Each release will be driven by well-defined objectives, aligning with the needs of our users and the goals of the organization.
Prioritization: Features and improvements will be prioritized based on their impact and importance, allowing us to address critical issues and provide meaningful enhancements with each release.
Flexible Scheduling: We will adopt a flexible scheduling approach that accommodates changes in priorities and unexpected developments, ensuring that our releases remain adaptive to evolving requirements.
Version Support
To ensure effective version support, we are implementing a revised strategy:
Defined Support Period: Each software version will be supported for a predefined period outlined in our calendar. This duration will ensure that users receive timely bug fixes, security updates, and compatibility adjustments.
Version Transition: With the release of a new version, support for the previous version will be maintained for 12 months. This will provide users with a transition period to migrate to the latest version while still receiving essential support for their existing installations.
Check the calendar here: #88
Versioning
Our revised versioning approach aims to provide clarity and consistency:
Semantic Versioning: We will adopt Semantic Versioning (SemVer) for our software releases. The version number will consist of three segments: MAJOR.MINOR.PATCH. Each segment will have a specific meaning:
Clear Communication: Version numbers will be accompanied by release notes that succinctly outline the changes in each release. This will facilitate a better understanding of what users can expect from each version.
Versioning Strategy
In our transition towards a more streamlined versioning process, we are discontinuing the use of labels like "godot4-v1.0.0" and "godot3-v1.3.3." Instead, we are introducing a more organized and standardized versioning approach.
New Versioning Format
Moving forward, each release will be identified using the format vMAJOR.MINOR.PATCH. This format provides a clear indication of the significance and content of each version.
Release Notes Enhancement
To enhance transparency and clarity, every version's release notes header will now prominently display the USED AND TESTED version of Godot. This ensures users are informed about the specific version of Godot that was employed during testing and development.
Example:
v1.3.4
Version used and tested: Godot 3.5.2
v2.0.0
Version used and tested: Godot 4.1.1
v3.0.0
Version used and tested: Godot 4.1.1
Handling Major Changes
In cases of significant changes, such as issue #82 (a MAJOR change), when multiple versions of Godot are still under support (e.g., Godot 3 and 4), it's important to note that only the most recent version of Godot (in this example, Godot 4) will support the newest features.
Disclaimer
Please note that our software is distributed under the MIT license, THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND.
Additionally, these rules and strategies may vary based on workforce availability or other related factors. We appreciate your understanding of the dynamic nature of software development and its associated considerations.
This will also be applied for these repositories:
Beta Was this translation helpful? Give feedback.
All reactions