Version Planning
Version Numbers and Codenames
The following is a list of Konado's version numbers and codenames:
| Codename | Version | Status | Release Date | Download |
|---|---|---|---|---|
| / | 3.0 | Planning | / | |
| Tieton | 2.3 | Active | 2026-03-05 | https://github.com/godothub/konado/releases/tag/v2.3 |
| Yuanxiao | 2.2 | Release | 2026-02-10 | https://github.com/godothub/konado/releases/tag/v2.2 |
| Lebkuchen | 2.1 | EOL | 2025-12-24 | https://github.com/godothub/konado/releases/tag/v2.1 |
| Mooncake | 2.0 | EOL | 2025-12-03 | https://github.com/godothub/konado/releases/tag/v2.0 |
Status Description
There are several version statuses for Konado:
- LTS: Indicates that this version is a long-term support version, which will provide longer technical support but usually fewer new features.
- Release: Indicates that this version has been released and can be used in production environments.
- Active: Indicates the latest or actively updated version, which will provide the latest features and fixes, but may have some unstable factors. Please carefully consider using it in production environments.
- Planning: Indicates that this version is being planned and collecting feedback, waiting for the official announcement of the plan.
- EOL: Indicates that this version has stopped maintenance, no longer updated and providing support and fixes. Please try to avoid using this version.
Version Release Time
Generally, Konado's version release time will be determined based on the following factors:
- Completion status of features and improvements
- Number of bugs fixed
- Community feedback and suggestions
- Release plan
Before releasing a new version, we will try our best to ensure the quality and stability of the new version, and ensure that the new version can meet the needs of most users.
Participate in Version Planning
We welcome you to participate in Konado's version planning. You can put forward your suggestions and opinions, and we will carefully consider and adopt your suggestions. If you have any ideas or suggestions, please feel free to submit Issues or Pull Requests.
If you want to put forward your suggestions through Issues, it is recommended to include the following key information:
- Expected features or improvements
- Reasons for adding this feature or improvement
- Solution description, including implementation method, expected effect, etc. (optional)
- Expected version number (which version should this feature or improvement be added to)
- Expected priority (high, medium, low), so that we can better arrange the development plan