| Home | Trees | Index | Help |
|---|
GNU Enterprise is under ongoing development, and once a new set of functions is ready to be used, a release is made.
Releases are numbered with a two-part release number, like 0.6 or 1.0 or 2.4.A build is a specific version of the software. For every release, several builds are made.
Before the release, so called "prerelease" or "unstable" builds are made. The version number of these builds consist of the release number of the upcoming release, a dash, the name of the phase of the release cycle, and the build number within the phase.
The first phase of the release cycle is "alpha", in which the software is expected to have bugs, and new features usually are freshly (and probably incompletely) implemented. As soon as the software is deemed feature-complete, it switches to "beta" phase, in which the bug hunting season starts. Once the developers feel that no serious bugs should be left over, the "pre" phase begins. In the last phase before the release, the versions are named "rc" (meaning "release candidate").
Then the software goes into the stable (read: end user suitable) phase. The first stable version of each release ends in ".0", but people will still find bugs or major improvements, and there will be further bug fix builds within the same release cycle, where the last number is incremented.| Classes | |
|---|---|
Version |
A version number consisting of several parts. |
| Function Summary | |
|---|---|
Find out the SVN revision of the last change in the current directory. | |
| Function Details |
|---|
get_svn_revision(directory)Find out the SVN revision of the last change in the current directory. The current directory must be an SVN checkout, and the "svn" command must be available. This function only works on POSIX systems. On other systems, it
returns GNUE_BUILD is set, the
function returns 0.
|
| Home | Trees | Index | Help |
|---|
| Generated by Epydoc 2.1 on Wed Jan 7 23:02:12 2009 | http://epydoc.sf.net |