summaryrefslogtreecommitdiff
path: root/DEVELOPERS.md
Commit message (Collapse)AuthorAge
* Improve release script with a focus on DebianGravatar Martin Frost2015-01-07
| | | | | | | | | - Fix obvious typos in `release.in`. - Build both binary and source Debian package. Also, make sure to run `debuild` in the actual build directory. - Add Debian source packages to gh-pages branch. - Put lonely `:` on its own line, to help it stand out. - Turn on signing for Debian source packages.
* Improve setup documentationGravatar Martin Frost2015-01-07
| | | | | | | Improve the `CONTRIBUTING.md` documentation about what dependencies exist, how to install them, and how to get started in general. Remind developers about the `configure` script, because without it no `Makefile` will exist.
* Add a release scriptGravatar Mike Burns2014-12-19
| | | | | | | | | The Makefiles were mostly filled with a complex shell script written in m4sh. Moving that out into a separate script helps debugging and compatibility, and in general makes life better. This also improved the DEVELOPERS.md documentation to be more clear about the steps of a release, including third-party packages.
* Expand on instructions for contributors to get startedGravatar Melissa Xie2014-11-24
| | | | | | | | These changes: * add the steps needed to get set up * update the docs regarding mandatory tests * clarify release instructions * fix documentation formatting
* Start bringing in the Makefile.am from gitshGravatar Mike Burns2014-02-26
| | | | | | | | | | | It introduces the `Makefile.am` from gitsh, and abstracts it a bit. This `Makefile.am`, or most of it, could be dropped into gitsh again. How to use it is documented in `DEVELOPERS.md`. The whole release process is more consistent and simple: `make release` to build a tarball, Homebrew, Arch, Debian, HTML (from manpages), and tag it, pushed to the various repos, and with cleanup. The `release` target is composed of smaller targets that stack well.
* Add a release targetGravatar Mike Burns2013-08-01
| | | | | | | | | | | | | The `make release` command will build the Debian package, push the version to a git tag on GitHub, and upload the docs to GitHub pages. This also adds a `deb` target, along with `build-docs`, `upload-docs`, `build-tag`, and `push-tag`. In addition, introduce a `NEWS.md` file. Both `rcm.sh.in` and `NEWS.md.in` will act as input files. This is to abstract over the version number.
* Document Debian installation instructionsGravatar Mike Burns2013-08-01
| | | | | Currently the deb file is hosted on my personal server. Download it then use `dpkg` to install it.
* Document how to generate the gh-pagesGravatar Mike Burns2013-07-30
| | | | | The mdocml tools, specifically mandoc(1), are used to generate the gh-pages HTML docs. This documentation is now documented.
* Able to generate deb packagesGravatar Mike Burns2013-07-27
| | | | | | | | | The following command can generate a Debian package: debuild -us uc The directory structure and tarball must be perfectly set up first. This is documented in `DEVELOPERS.md`.
* Re-write using GNU autoconf and automakeGravatar Mike Burns2013-07-27
Replace the `Makefile` with a `configure.ac` and a set of `Makefile.am`.