aurae-runtime / release

Release

This repository will maintain the releases for the aurae project.

Project Status

The project is very young and under active development. The APIs are subject to change without notice until further notice. As we continue to develop the project the APIs will stabilize and eventually a long term stable release will be offered.

At this time the project should not be run in production.

Please read getting involved if you are interested in joining the project in its early phases. Contribution types of all types and ranges are welcome.

Release Artifacts

Note: some of these links may not function until we release the first build

The following artifacts will be available with every stable build. While we are in alpha, only artifacts that share the same version are known to be compatible.

Build	Architectures	Artifacts	Status
auraed	x86_64-unknown-linux	Releases
auraescript	x86_64-unknown-linux	Releases
aer	x86_64-unknown-linux	Releases
ae	x86_64	Releases

Release Process

The instructions to cut a release are available in the RELEASE.md.

Support

Please check out our FAQ section to see if it might help address your issue. Our website also has information that may help.

Support is also available via the following channels

• Discord

Bugs

Please create an issue in the appropriate project repository. Links to those repositories are avaiable in the Release Artifacts table above.

• Provide a clear description of the bug
• Provide any steps required to reproduce
• What behavior are you expecting
• Any error messages

Security issues

Do not open a public issue if you find a security issue.

Please notify us privately at EMAILHERE. We will investigate and respond as soon as possible.

release's Issues

Releases listed on website

How do we balance releases on GitHub with the https://aurae.io website?

Do we intend to generate links from the GitHub servers and embed the links directly into the website?

Modify cargo.tomls

The cargo.tomls should be modified to reflect the release version.

Container images

Do we intend to release any container images along side the release artifacts?

Release hashes

We should make sure we include the hash of each artifact released in the notes.

How to cut a release documentation?

Is there documentation anywhere on how someone like myself can cut a release?

Version documentation

How do we balance our documentation with our version numbers? What if we release Aurae 1.0 and then later release Aurae 2.0? Which version of the documentation will be available online? Will we be able to "toggle" between the various versions?