Skip to content

Nightly builds, rolling release

Pre-release
Pre-release
Compare
Choose a tag to compare
@aurelienpierre aurelienpierre released this 13 Dec 21:57
· 913 commits to master since this release
17343ac

Welcome

This "virtual" release will get updated with the packages produced by the nightly builds.

Nightly builds are done automatically every night at 00:00 UTC for the master branch ("fairly stable" channel), and build packages for : 

  • MacOS (.dmg package) soon,
  • Windows (.exe package), for Windows 10 et 11
  • Linux (.AppImage package), for any distribution packaging at least glibC 2.31 (Ubuntu 20.04, Debian 11, Fedora 32, openSUSE 15.3, ArchLinux, etc.).

This is meant for continuous testing and continuous delivery, in a "quickly broken-quickly fixed" way. Learn more about Ansel channels.

For maximum stability, you should wait for production releases.

Understanding packages name

All packages follow the same naming convention : ansel-x.y.z+N.g000000000-architecture.extension:

  • x.y.z is the tag of the latest stable release. It will always increase with time and helps you determine how old or recent a package is compared to the one you have installed.
  • +N is the number of commits on the branch since the latest stable release. It will always increase with time and also helps you determine how old or recent a package is compared to the one you have installed.
  • .g means the package comes from Git directly,
  • the nine 000000000 following .g are the unique ID of the most recent commit. Those are a random hash which follows no particular logic, however it is very useful to communicate for debugging purposes because it defines a particular state in the history of the source code. It can be found in the Git log.
  • architecture tells you if the package is built for your CPU, it typically contains 64 which means a 64 bits architecture suitable for all Intel CPU since 2006 or so,
  • .extension is the OS-flavored package, so .dmg or .exe or .AppImage.

The .AppImage.zsync files are meant for auto-updaters, to allow incremental updates, they need to be here for technical reasons but end-users should not care about them (don't download, don't use, don't worry).