That doesn't make much sense. In what kind of versioning scheme does a release not contain the same code as the stable branch in a specific version?
In that case calling them "Release notes" is even more confusing...
In that case calling them "Release notes" is even more confusing...
Here is an explanation:
- RELEASE is actual release that is forked out (it will only contain security and other critical fixes) of the STABLE branch.
- STABLE is just a development branch (currently it is anything in version 10) as opposed to CURRENT which is a bleeding edge.
- CURRENT is what will be next version (version 11), once they finish adding features it will become next STABLE branch and CURRENT will be used for version 12.
While everything that ends up at STABLE needs to go through pointyhat build system, so it should always compile and pass regression testing, there's still a possibility of things breaking up.
Since 10.0 is about to be released STABLE contains what will become 10.1.
Here's example how the branches look like:
----------------- CURRENT (version 11)
\
-STABLE (version 10) ---
\ \
- 10.0-RELEASE - 10.1-RELEASE
\ \
-p1 -p2
Since 10-RELEASE was just cut it's probably close (identical?) to 10-STABLE, but that won't last long.
It is confusing, however, but there is some logic to it.