Fulltext results:
- developer_guidelines
- ker issue). Your commit message should contain //tags// that describe the type of commit (e.g. ''Fixed'... d by the commit. You can see many examples of the tags by examining the Git history. The commit tags serve a couple of purposes: * At-a-glance summary of w... Index the commits in the [[:codex]]. While the tags are not checked for validity, you should generall
- automated_build_system
- if the master branch has new commits, and if so, tags and builds a new release. The releases become ava... bed above. Alternatively, there are prebuilt .deb packages available in [[https://launchpad.net/~sjke/+arch... able : A **stable** build is one which has been packaged for widespread distribution and has been extensi... ts to generate an installable binary distribution package under //distrib/releases//. The script takes no
- compiling_and_running_2.0
- * Download a [[http://dengine.net/source|source package]]. * Check out the [[https://github.com/skyjak... hen switch to any release or a specific build via tags. Stable releases are tagged "release-x.y.z". ===