Changes between Version 40 and Version 41 of WikiStart


Ignore:
Timestamp:
Jun 16, 2010, 8:42:41 PM (14 years ago)
Author:
David Azarewicz
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v40 v41  
    1010Download:
    1111
    12 The current stable binary release is 1.9.22.
     12The current stable binary release is [ftp://ftp.netlabs.org/pub/uniaud/Uniaud191-1922.zip 1.9.22].
    1313
    14 Download links coming soon...
    15 
     14The debug version of this release is [ftp://ftp.netlabs.org/pub/uniaud/UniaudDebug191-1922.zip here].
    1615
    1716= Getting the sources =
    … …  
    6362== Uniaud16 ==
    6463
    65 Public builds of uniaud16.sys are included with 1.1.4RCx packages, with the installer, uniaud32.sys of the same version, and other related files. There should not usually be a reason to publicly release Uniaud16 by itself, because any time Uniaud16 is improved it is probably a good time to release a complete package anyway. See [ReleaseProcedures Release Package Procedures] for how we go about this.
     64Public builds of uniaud16.sys are included with all uniaud packages. There is not usually be a reason to publicly release Uniaud16 by itself. See [ReleaseProcedures Release Package Procedures] for how we go about this.
    6665
    6766When distributing builds of Uniaud16 privately to a few people to test, a good practice, to avoid confusion with the public releases, is to change the "fixpak level" to the svn revision number, e.g. "!r380". If it does not match any revision number, perhaps because you are testing before committing, you may want to distinguish it with a word like "TESTCASE" or "CUSTOM". None of these labels for private builds should be committed to the svn repo. It is also helpful to set the HOSTNAME environment variable to a unique word that can trace the build back to you if your build system's hostname doesn't already.
    … …  
    6968== Uniaud32 ==
    7069
    71 Trunk (1.1.4) releases of Uniaud32 accompany Uniaud16 of the same version, so public releases follow the same [ReleaseProcedures Release Procedures].
     70Trunk releases of Uniaud32 accompany Uniaud16 of the same version, so public releases follow the same [ReleaseProcedures Release Procedures].
    7271
    7372The same practices for private builds apply as well, except that Uniaud32 is GPL, so for license compliance any test builds that are distributed privately should not only specify the svn revision number, but also include a patch against that revision if anything differs. This is easily acquired with: