Experimental: Difference between revisions
mNo edit summary |
(Added noinclude tags, and version category.) |
||
Line 3: | Line 3: | ||
C:DDA, does have an automatic build system that creates new experimental versions (called builds) every day there are changes (aka, pull requests on github being merged). Or you can build it yourself. All of these are called experimental versions. Don't try to differentiate between different experimental builds on the wiki. That just makes it confusing for people reading it later. (And don't even refer to the experimental version directly. Use the [[Template:ver]] or [[Template:InlineVer]] for that (So it gets automatically updated when there is a new release). | C:DDA, does have an automatic build system that creates new experimental versions (called builds) every day there are changes (aka, pull requests on github being merged). Or you can build it yourself. All of these are called experimental versions. Don't try to differentiate between different experimental builds on the wiki. That just makes it confusing for people reading it later. (And don't even refer to the experimental version directly. Use the [[Template:ver]] or [[Template:InlineVer]] for that (So it gets automatically updated when there is a new release). | ||
<noinclude> | |||
== Where to get it == | == Where to get it == | ||
Line 32: | Line 33: | ||
This is a page describing what the experimental build is. Not what has recently changed. There is no actively maintained list of changes for the experimental version on the wiki. | This is a page describing what the experimental build is. Not what has recently changed. There is no actively maintained list of changes for the experimental version on the wiki. | ||
[[Category:Versions]] | |||
</noinclude> |
Revision as of 20:37, 4 August 2016
The most current version on github is called the experimental version, or trunk. It is the version actively being developed, and the version for which we try to keep the wiki up to date.
C:DDA, does have an automatic build system that creates new experimental versions (called builds) every day there are changes (aka, pull requests on github being merged). Or you can build it yourself. All of these are called experimental versions. Don't try to differentiate between different experimental builds on the wiki. That just makes it confusing for people reading it later. (And don't even refer to the experimental version directly. Use the Template:ver or Template:InlineVer for that (So it gets automatically updated when there is a new release).
Where to get it
There are several ways to get the most recent experimental builds.
Compile it yourself
See How to compile for some outdated instructions. Better is to check COMPILING.md, if you need help you can ask on the forums or the IRC channel. But don't expect people to hold your hand.
Download the latest Jenkins build
- Windows
Download Windows (Graphical Experimental)
Download Windows (Console Experimental)
- Linux
Download Linux (Graphical Experimental)
Download Linux (Console Experimental)
Why is there no build number X for my OS?
Sometimes there can be an experimental build for one OS and not for the other, this is due to the automatic build process failing for one specific OS. Don't worry, it will be fixed, and a new build will be up later (Can take some time however, but the developers try to keep all the automatic build processes working.
What has changed
To see what has changed recently you can look at the recently merged pull requests, or look at the recent Jenkins changes] to see what has changed for each specific experimental build.
What is this page? I wanted a list of changes for the latest experimental build
This is a page describing what the experimental build is. Not what has recently changed. There is no actively maintained list of changes for the experimental version on the wiki.