Green

20 July 2014

- Implemented custom test discovery code instead of relying on built-in
unittest.discover(). So far, the new implementation mimics the built-in
behavior except for fixing issue 14 (which unblocks 7). This enables working
on 25 and any other bugs or behavior that was locked inside of unittest's
quirky discovery implementation that we want to fix in the future.

- Fixed travis config to exclude the example project in builds.

- Reduced debug timestamp precision from microsecond- to second-based.

- Exclude colorama from coverage reporting for the sake of Windows users.

- Added some additional internal debug output.

- Centralized internal debugging output.

- "make clean" now cleans all `.coverage*` files in the project tree.

- Many new internal tests.

17 July 2014

- Configuration file support, originally contributed by Tom Barron - Issues
20, 23, 24

6 July 2014

- Color works on Windows - Issues 18, 19

- Self-tests run against installed versions automatically - Issue 10

- Installation process is now tested automatically - Issue 9

- Switched to "branch-based development"

- Added an "example" directory with an example project with unit tests

- Added the CHANGELOG (this file)

- Improved the README.md file a lot based on feedback from reddit.

23 June 2014

- Fixed MANIFEST so that installation didn't crash

- There were lots of versions before 1.0 was released (54 published releases,
actually). No one heard about it before 1.0 though, so we didn't bother
tracking individual releases.


Steps to Release
================

1. Bump the version in `green/VERSION`, per [PEP 440](https://peps.python.org/pep-0440/).

2. Push and merge to the main branch.

3. Trigger the Release Test workflow in GitHub Actions then approve the run on the release-test environment. Optional but recommended.

4. Create a new release in GitHub with a tag that mirrors the version, the GH action will take care of the rest after beeing approved to run.