by Enjay » Mon Jul 08, 2013 19:58
Old message kept for posterity...
[spoiler]Unmodified builds
Written by: Enjay
Build files named "rXXX(yyy).zip"
example: gzdoom-r228(229).zip
To make people aware of what that means, I'm doing this when the version of the exe doesn't match the head revision number from the SVN repository. In this case, the exe is revision 228 but the head revision is 229 because Graf has made some changes outside the source. These changes do not affect the exe, but do bump the SVN head revision number.
I'm doing this just in case people are keeping an eye on the SVN repository and perhaps noticing that the revision number is higher than the one the exe is reporting itself as, or that the compiled file online is apparently behind the revision status of the repository.
Build files named "rXXXm.zip"
example: zdoom-r1424M.zip
As many of you will know, the "m" stands for "modified", indicating that the source used to make the build was modified from the source on the SVN server.
I wouldn't normally put a modified build up unless there is a bug with the unmodified version that prevents if from starting.
When this happens, I have applied a change to the code to allow people to use the latest build. This change is exactly the one that either Graf or Randy will commit to the SVN repository when they can. However, the number, at that point, will not be what's listed, but whatever it gets bumped to (presumably one higher).
Experimental builds
Written by: Gez
Build files named "rXXXm_<bug>fix.zip"
example: zdoom-r1624m_loaddirfix.zip
This contains an experimental fix to a bug recently introduced or discovered. The build is otherwise identical to the official one upon which it is based.
Build files named "<mod>_rXXXm.zip"
example: stcompat_zdoom-r1625m.zip
This contains new features and may deviate significantly from the official build upon which it is based. The zip may contains as well additional material to help test the new features. A thread in the Experimental Builds forum provides more information on the build.
For both types of experimental builds, a patch file is usually included.[/note][/spoiler]
Old message kept for posterity...
[spoiler][size=200][headereffect=#00FF10]Unmodified builds[/headereffect][/size]
[size=50]Written by: Enjay[/size]
[size=150][headereffect=#FF0010]Build files named "rXXX(yyy).zip"[/headereffect][/size]
example: gzdoom-r228(229).zip
To make people aware of what that means, I'm doing this when the version of the exe doesn't match the head revision number from the SVN repository. In this case, the exe is revision 228 but the head revision is 229 because Graf has made some changes outside the source. These changes do not affect the exe, but do bump the SVN head revision number.
I'm doing this just in case people are keeping an eye on the SVN repository and perhaps noticing that the revision number is higher than the one the exe is reporting itself as, or that the compiled file online is apparently behind the revision status of the repository.
[size=150][headereffect=#FF0010]Build files named "rXXXm.zip"[/headereffect][/size]
example: zdoom-r1424M.zip
As many of you will know, the "m" stands for "modified", indicating that the source used to make the build was modified from the source on the SVN server.
I wouldn't normally put a modified build up unless there is a bug with the unmodified version that prevents if from starting.
When this happens, I have applied a change to the code to allow people to use the latest build. This change is exactly the one that either Graf or Randy will commit to the SVN repository when they can. However, the number, at that point, will not be what's listed, but whatever it gets bumped to (presumably one higher).
[note][size=200][headereffect=#00FF10]Experimental builds[/headereffect][/size]
[size=50]Written by: Gez[/size]
[size=150][headereffect=#FF0010]Build files named "rXXXm_<bug>fix.zip"[/headereffect][/size]
example: zdoom-r1624m_loaddirfix.zip
This contains an experimental fix to a bug recently introduced or discovered. The build is otherwise identical to the official one upon which it is based.
[size=150][headereffect=#FF0010]Build files named "<mod>_rXXXm.zip"[/headereffect][/size]
example: stcompat_zdoom-r1625m.zip
This contains new features and may deviate significantly from the official build upon which it is based. The zip may contains as well additional material to help test the new features. A thread in the Experimental Builds forum provides more information on the build.
For both types of experimental builds, a patch file is usually included.[/note][/spoiler]