A standard to easily communicate to humans and machines the development/support and usability status of software repositories/projects.
Please feel free to leave comments as Issues, or open pull requests.
For changes to the site, text, or anything other than the badges themselves (and their descriptions and sample markup),
simply cut a pull request against the master branch. The content that appears on the website (in the gh-pages branch)
gh_pages/ in master. Note that some of it (described below) is generated programmatically.
The badges (SVG), their descriptions and their sample markup are generated by a Fabfile. If you're looking
to add a new badge or make changes to an existing one, simply update the
badge_info dictionary at the top of
fab make_badges (requires Python and some packages; see the comment at the top of the file for requirements). This will
regenerate all badges, metadata and samples into
badges/latest. You can then cut a pull request for this; a version number will
be assigned at merge time. Please remember to also update
gh_pages/index.md for any badge changes.
- Get everything included in the release merged into master.
- Assign a version number. In general, patch versions should only be assigned for releases that fix trivial (i.e. spelling) issues or touch things other than the badges and JSON (i.e. the markup samples). Minor versions should be assigned to changes that correct grammatical or spelling errors, or graphical elements. Major versions must be assigned to any changes that add or remove badges, or alter the meaning of existing badges.
fab make_badgesand ensure there are no new changes.
x.y.zis the version number).
- Add a
fab badges2pagesto copy the badges under
fab publishto push changes to the gh-pages branch.
- Review the diff of gh-pages against origin.
- Assuing all is well, push gh-pages to origin. The changes are now live.
- Tag master with the version number (use GitHub Releases)