Breaking release

[mortenpi]

It looks like we're heading towards a breaking release. We should try doing as many breaking changes together as possible, to make our lives easier. Right now I can think of these (but additional suggestions are very welcome):

• Changing makedocs(format=:html)
• Changing deploydocs(julia=...). (Make deploydocs(julia=...) mandatory #526 / Default deploydocs to release #466; depwarn in Make julia a required kwarg in deploydocs #712)
• Don't use the release-x.y directories. (stop deploying to the release- folder #706)
• Other versioning changes (ref: Changes to docs deployment conventions JuliaLang/julia#26825, Add selector argument to deploydocs #813)
• Remove julia and osname arguments to deploydocs() and promote Travis build stages instead ( Remove julia and osname kwarg from deploydocs #816)
• Update message (https://discourse.julialang.org/t/displaying-an-update-message/12577) -- problematic with new Pkg.

Additional non-coding tasks we need to do before we can release this:

• Automated PRs against METADATA packages using Documenter.
• Need to ANN this on Discourse, ideally a reasonable time before the release hits METADATA.

The automated PRs could just add an upper bound to Documenter's Pkg.add. We could also consider actually making the necessary fixes to make.jl etc.

---

We also need to tag the new packages:

• DocumenterTools.jl
• DocumenterMarkdown.jl
• DocumenterLaTeX.jl

[fredrikekre]

The automated PRs could just add an upper bound to Documenter's Pkg.add. We could also consider actually making the necessary fixes to make.jl etc.

I think with we should recommend people to make a doc-build project in e.g. docs/Project.toml, and commit its Manifest.toml. That way one needs to explicitly call up to update Documenter.

[mortenpi]

I would go with the middle ground and have user have a [compat] section in their Project.toml to fix the major version. That way they would still get bugfixes.

[mortenpi]

TODO list for the mass PRs for setting upper bounds -- summarizing our discussion @fredrikekre:

• (1) Draft the issue, PR and discourse PSA
• (2) Gather a list of packages we need to PR and see what we need to do exactly.
• (3) Create an issue on Documenter for tracking the PRs. We should also lock the conversation there and suggest that people subscribe to that issue to be notified when v0.20 is released. The only thing that should be posted there is the announcement that v0.20 has hit METADATA. Other conversation should happen here in Breaking release #713 (or Discourse).
• (4) Make all the PRs. Make sure they refer to the issue created in (3).
• (5) Also PR all the documentation-only repos we have. Probably manually.
• (6) Post a Discourse PSA after the PRs have been done. So that in case we missed something or for private packages etc., people would also know what to do if they need to do it by hand.