Skip to content
Doug Goldstein edited this page May 22, 2018 · 10 revisions

Welcome to the meta-rust wiki!

Maintainer Rules

Issue / PR Tagging

R-yoctoreleasename labels are used on issues where they affect things or on PRs where they should be merged.

There are then 6 additional tags that can be applied to an issue:

  • question - should this be done or not?
  • enhancement - a request for improvement
  • bug - an issue with something in the repo
  • meta - relates to project management
  • help wanted - anyone knowledgable in this area is requested to assist
  • patches welcome - none of the maintainers are actively looking to fix this and the community is encouraged to provide a patch

Merging PRs

A PR must run through CI and pass successfully. If the change is something that would not be run by the existing CI loop then there should be some notes on how the change was verified to be correct. Consideration should be made to whether the existing CI loop should be enhanced to test this use case to ensure it does not regress. A PR must have an approved review by another maintainer and can be merged in by another maintainer. If two maintainers approve the PR then you are welcome to merge your own PR in.

Supported Versions

The maintainers of this layer do so on a voluntary basis. There is no known commercial support of this layer however there are a number of commercial entities utilizing it, as a result users are encouraged to provide as much feedback and support as they are able to with the knowledge that the maintainers are voluntary.

Branches supporting different Yocto releases are supported for as long as there is maintainer effort to support them, this typically results in about 2 Yocto releases receiving support. There may be situations where a Yocto release may be supported and a newer release may not be supported due to available manpower and resources however.

Rust versions will be supported in a fashion to make it easy to upgrade Yocto releases. When Yocto release X has Rust versions A and B where B > A. Then Yocto release X + 1 should contain at least Rust version B. It may also contain Rust version C where C > B. Assuming Yocto release X + 1 did contain Rust release C then Yocto release X + 2 should contain Rust release C but not B. A concrete example would be:

Yocto Release Legacy Stable
krogoth 1.10.0 1.12.1
morty 1.12.1 1.15.1
pyro 1.15.1 1.20.0
rocko 1.20.0 1.24.1
sumo 1.24.1 1.C.D
NEXT 1.C.D 1.E.F
Clone this wiki locally