Development Rules

Development Rules

Code style

We generally follow Linux Kernel code style for C code but we are not really strict on this. Just make sure it's not something looks like win32.

Contributions

• We are using GitHub Pull Requests to accept contributions.
• Any collaborator of the project can accept pull requests.
• For contribution from collaborators you are encouraged to ask review from another collaborator before approving the change.
• No direct commit into main branch despite trival fixes.
• If you have a history of contribution and want to become a collaborator please reach @FlyGoat.

Release

Version policy

We are using x.y.z style version number. x is used to indicate fundamental change in architecture, y is used to indicate any ABI change, z is used to indicate small fixes.

Releasing

• Any collaborator can draft a new release.
• Version number in lib/ryzenadj.h must be changed before release.
• Changelog must be filled on Github release page, please use previous releases as reference.
• Release artifiacts must come from GitHub action for reproducibility.
• Collaborators are encouraged to let other collaborators aware plan of release in advance, however this does not have to be formal, comments under issues are sufficient.