diff options
| author | Jan Niklas Hasse <jhasse@bixense.com> | 2019-08-30 11:07:58 (GMT) |
|---|---|---|
| committer | Jan Niklas Hasse <jhasse@bixense.com> | 2019-11-24 11:58:31 (GMT) |
| commit | a37da20ae74c81703b1c811182fc154d95ed46fe (patch) | |
| tree | d1638a3a01b775c2c8ef05f39c7c02932d3c062e /RELEASING | |
| parent | 6ee71118b87935c6629f69a41bfa531925ef44c2 (diff) | |
| download | Ninja-a37da20ae74c81703b1c811182fc154d95ed46fe.zip Ninja-a37da20ae74c81703b1c811182fc154d95ed46fe.tar.gz Ninja-a37da20ae74c81703b1c811182fc154d95ed46fe.tar.bz2 | |
Use short CONTRIBUTING.md instead of HACKING.md
* Only the most important parts and some new guidelines in
CONTRIBUTING.md.
* Complete HACKING.md content moved to the GitHub wiki:
https://github.com/ninja-build/ninja/wiki
* README is now also Markdown formatted.
Diffstat (limited to 'RELEASING')
| -rw-r--r-- | RELEASING | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -1,7 +1,7 @@ Notes to myself on all the steps to make for a Ninja release. Push new release branch: -1. Run afl-fuzz for a day or so (see HACKING.md) and run ninja_test +1. Run afl-fuzz for a day or so and run ninja_test 2. Consider sending a heads-up to the ninja-build mailing list first 3. Make sure branches 'master' and 'release' are synced up locally 4. Update src/version.cc with new version (with ".git"), then |