slip tags explanation


Matt Dillon posted more ideas on how the DragonFly releases were to go. Specifically, different versions would be coded by slip tags instead of the branches that go on with FreeBSD:

releaseX_Y: Specific official release, build and regression tested, including security fixes. A sub-sub version (Z) would be embedded in the uname to differentiate between updates to a release, but not be incorporated into the tag name.

release: Current official release.

developer: Developers who want to be cutting edge but still be ‘reasonably’ stable, with occassional glitches.

HEAD: Absolute latest work, might have build and other issues.

Not being branches, slip tags are limited in scope. It might not be possible to incorporate a security fix into a particular release tag, for example, all we would be able to do is tell people to upgrade to a later release. When we are able to stabilize the system interfaces (about a year and a half from now) this won’t be a big deal.”

Posted by     Categories: Goings-on     0 Comments
0 Comments on slip tags explanation

Closed