You know that the current ABCD is maintained in GitHub. Hundreds of commits have improved and extended the code of ABCD.
Up til now there was only minimal attention for release management.
Since the last release (v2.2.0-beta-1 in 2022) ~850 commits were included and this is too rough.
We feel that more regular releases are required.
We will try to adhere to the semantic versioning concept with a numbering scheme: Major.Minor.Bug-fix.
E.g.
- An update from v2.5.2 to v2.5.3, is just a bug fix and you can update with confidence.
- An update from v2.5.3 to v2.6.0, indicates new features and you may need to read the release notes.
- An update from v2.6.0 to v3.0.0, is a major change and you will need to plan the update more carefully.
We will start this new release numbering soon with start version 2.3.0 as we assume that you are all using the latest code downloaded from GitHub and this release fixes some bugs and the first version of new feature ‘Updater’.
This new ‘Updater’ that will help in updates.
This updater is in development and you should yet rely on this tool until it is ready.
In order to avoid confusion between the repository name and and the ABCD versioning repository ABCD2 will be renamed to ABCD.
Implications:
- If you have a bookmark in your browser: you have to change it
- If you have forked the repository: GitHub will keep the link
- If you have GitHub Desktop: you can clone the project via Code –> Open with GitHub Desktop (the red arrows in the picture)
- If you are using the GitHub API you should use the new URL (The blue arrow points to the URL. The new URL will show ABCD in stead of ABCD2)
- For other situations: the internet is your friend and explains several other scenarios
