Release v0.7.0

[cbm755]

@catch22 maybe we should think about release b/c of the Makefile bug you found...

TODO list

• resolve tests can change the current working directory #117 and tests can change the default output format options #183
• Add tests for octfile support #181 would be nice to have but maybe not essential?
• test on Matlab
• test on new Octave 5.1
• double-check what Octave versions we're running on CI these days...
• resolve all milestone 0.7.0 issues/PRs
• Update NEWS
• Update DESCRIPTION
• Tag git commit once accepted upstream [this isn't done by us]
• After release, push tags to github
• Do github release.

This is not 1.0 b/c of e.g., #181, testing mex files, manual, bikeshedding doctest_collect, etc.

[catch22]

👍

[mtmiller]

Just noting that #189 doesn't affect users or pkg install, it's only the maintainer Makefile install rule for development that is affected.

[cbm755]

Filed upstream at https://sourceforge.net/p/octave/package-releases/373/

Octave Forge releases are back logged, I've been trying to help by reviewing other release candidates but more help is always needed.

[catch22]

I added three todo items above. Perhaps this can only go into 0.7.1.

Possibly https://github.com/catch22/octave-doctest/wiki/Development-Process#checklist needs updating.

[cbm755]

Was there something wrong with NEWS and DESCRIPTION? Should I check those off the list? (I tried to follow the release process on the wiki)

[catch22]

Gah, I think I looked at an old checkout when grepping for Version and seeing 0.6. Very sorry about that..