Prepped for tagging a v0.8.0 release of Javis

[TheCedarPrince]

PR Checklist

If you are contributing to Javis.jl, please make sure you are able to check off each item on this list:

• Did I update CHANGELOG.md with whatever changes/features I added with this PR?
• Did I make sure to only change the part of the file where I introduced a new change/feature?
• Did I cover all corner cases to be close to 100% test coverage (if applicable)?
• Did I properly add Javis dependencies to the Project.toml + set an upper bound of the dependency (if applicable)?
• Did I properly add test dependencies to the test directory (if applicable)?
• Did I check relevant tutorials that may be affected by changes in this PR?
• Did I clearly articulate why this PR was made the way it was and how it was made?

Link to relevant issue(s)
Closes N/A

How did you address these issues with this PR? What methods did you use?

As a result of PR #451, since this is a breaking change, we should probably release a new version of Javis.
I went ahead and updated the Changelog as well as Project TOML for the release.
Any more PRs or features we want to introduce before we release a new version?
Maybe we should try to get #399 in as well?

[codecov-commenter]

Codecov Report

Merging #458 (9b9feca) into master (b7f78a4) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #458   +/-   ##
=======================================
  Coverage   96.47%   96.47%           
=======================================
  Files          35       35           
  Lines        1617     1617           
=======================================
  Hits         1560     1560           
  Misses         57       57           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b7f78a4...9b9feca. Read the comment docs.

[Wikunia]

LGTM though JavisNB doesn't seemed to be tagged yet, right?
I wouldn't wait for #399 for this release

[gpucce]

@Wikunia @TheCedarPrince I have never tagged a release, if we choose to go on before #399 I'd like to do it myself so I know how it works. In case it is complicated or there are things to be particularly careful about you can point me to those.

[Wikunia]

This has to be installed:
https://github.com/JuliaComputing/Registrator.jl#install-registrator
I just checked and it is for all repos of this organization.

Then you need to make sure that the Project.toml is correct (has version 0.1.0, has compat bounds for every package it depends on)
Afterwards you should be able to simply open an issue called releases (actually doesn't matter how you call it)
and call @JuliaRegistrator register() as you can see here: #113

Afterwards a new issue on the JuliaRegistry should be created (the bot will answer your comment in the issue where you called register. We need to wait for 3 days until it is registered.

Then we can continue with v0.8 here

[gpucce]

Ok then tomorrow I will do it. Now it would be impossible without mistakes somewhere.