Software

Downloads

Stable installers and packaged releases should be distributed through GitHub Releases. The website can link to those release assets without storing large binary files inside the static site repository.

GRACE Level-2 Processing Software

Publish each installer as a versioned release asset, then keep this page pointed to the latest stable release or to a specific verified version.

Open GitHub Releases

Recommended distribution rule

  • Use GitHub Releases for `.exe`, `.msi`, `.zip`, or installer packages.
  • Keep the website repository focused on source code, pages, and small static assets.
  • Use semantic version labels such as `v0.1.0`, `v0.2.0`, or `v1.0.0`.

Before publishing

  • Record the version, release date, supported Windows version, and checksum.
  • State whether the package is an installer, portable build, or source archive.
  • Test the download link after GitHub Pages finishes deployment.