About
Introduce the context behind the work.
Project Scope and Timelines
Define the requirements, the work being done, and by when the work ought to be completed.
Components and Repos
Identify repos and components that work will include. Include any proof-of-concepts and existing patchwork as well.
Stakeholders and Partners
Who needs to be included in design, implementation, review or testing? Include here RISE contacts (using @PersonName) and external parties (other partners, key upstream project contacts)
Dependencies
Do you depend on something being done in another WG? Do you need some spec work?
Measure of Success
How will the Board know the project succeeded?
RISE Requirements
What do you need from the RISE Board?
Status Updates
Add key updates here, using heading 2 with the update date as the title.There is today a functional port of the Go Runtime on RISC-V. However, in order to guarantee the stability of Go on RISC-V, we want to make sure that Go is regularly built and tested on RISC-V, and even preferably as part of the official build and CI system of Go.
https://farmer.golang.org/builders#host-linux-riscv64-unmatched
New Swarming CI:
Linux/riscv64
freebsd/riscv65
Status Updates
| Page Properties | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|