Check docs coverage for dvc 2.8

[iesahin]

This is a tracking issue to check whether the following new features and bug fixes (should) have corresponding docs updates/PRs.

🚀 New Features and Enhancements

• Fix exp show --sort-by issue exp show --sort-by: not working dvc#6675 (Fix exp show --sort-by issue #6675 dvc#6764) @eggqq007
• webhdfs: migrate to fsspec (webhdfs: migrate to fsspec dvc#6662) @isidentical
• hdfs: migrate to fsspec (hdfs: migrate to fsspec dvc#6604) @isidentical
• command: Should not consume 'print' to output default remote info (command: Should not consume 'print' to output default remote info dvc#6650) @eggqq007
• command: output prettify json in tty (command: output prettify json in tty dvc#6743) @eggqq007
• Run on Python3.10 (Run on Python3.10 dvc#6745) @skshetry (document Python version requirements? #2975)
• http: explicitly retry all http-related errors (http: explicitly retry all http-related errors dvc#6728) @isidentical
• exp init: introduce --with={default,live} flag (exp init: introduce --with={default,live} flag dvc#6716) @skshetry (ref: Document dvc exp init #2974)
• cli: add short alias for --show-{csv,json,md} (cli: add short alias for --show-{csv,json,md} dvc#6711) @skshetry
• command: Show dvc list output in pretty JSON format (command: Show dvc list output in pretty JSON format dvc#6647) @eggqq007
• exp init: show heading based on the presence of dvc.yaml file (exp init: show heading based on the presence of dvc.yaml file dvc#6701) @skshetry
• exp init: support interactive and explicit options (exp init: support interactive and explicit options dvc#6681) @skshetry
• better exception messages for schema errors (better exception messages for schema errors dvc#6679) @skshetry
• ui: support pager universally (ui: support pager universally dvc#6692) @skshetry
• add alias ls for dvc list (add alias ls for dvc list dvc#6683) @ap-kulkarni
• remote: add support for Amazon S3 timeout configuration (remote: add support for Amazon S3 timeout configuration dvc#6634) @whysage
• merge yaml parsing and schema validation into one, aka strictyaml.load (merge yaml parsing and schema validation into one, aka strictyaml.load dvc#6661) @skshetry
• exceptional exceptions (exceptional exceptions dvc#6654) @skshetry
• Allow user to specify different state and index tmp dir locations (Allow user to specify different state and index tmp dir locations dvc#6419) @nueschs

🐛 Bug Fixes

• Fix exp show --sort-by issue exp show --sort-by: not working dvc#6675 (Fix exp show --sort-by issue #6675 dvc#6764) @eggqq007
• gs: use 3-char prefixes (gs: use 3-char prefixes dvc#6759) @isidentical
• Fix dvclive running subdir (Fix dvclive running subdir dvc#6740) @daavoo
• build(setup): avoid leaking tests package into site-packages (build(setup): avoid leaking tests package into site-packages dvc#6585) @pwoolvett
• doctor: fixes unknown cache directory error on some windows mapped network shares (doctor: fixes unknown cache directory error on some windows mapped network shares dvc#6364) @anasitomtn
• http: allow reading proxies from the current environment (http: allow reading proxies from the current environment dvc#6688) @isidentical
• ssh: fix path normalization on windows (ssh: fix path normalization on windows dvc#6517) @isidentical
• ssh: bundle bcrypt by default (ssh: bundle bcrypt by default dvc#6678) @isidentical
• fix dvc[all] (fix dvc[all] dvc#6657) @casperdcl
• progress: do not block on async filesystems (progress: do not block on async filesystems dvc#6612) @isidentical

[iesahin]

Waiting for @skshetry 's response in iterative/dvc#6692.

Created #2975 and #2974 for this.

[skshetry]

@iesahin, please sanitize the changelog next time, i.e remove contributors' mentions, this sends a spam notification to the contributors. Also, are we going to do this regularly from now on?

[iesahin]

Ah, sorry, @skshetry. I should have thought it.

@jorgeorpinel was doing this before, this time I decided to take over but with much unnecessary noise, it looks.

I try to do much of these work in the open. I don't know what we'll do for the next release, but we may continue to do it. These do not replace the docs PR requirements BTW, just a double check we're not missing anything.

Thank you, and sorry again.

[jorgeorpinel]

Thanks @iesahin I'm not 100% convinced we need issues for these although I guess it's better to formalize all the things we already do anyway (like this). Should def. not re-mention all the PR authors though, as we all agree.

It's probably enough to link to the release (i.e. https://github.com/iterative/dvc/releases/tag/2.8.0) and only add checkboxes for anything that's missing.

are we going to do this regularly from now on?

Yep, been doing it for a ling time informally, at least for new features and relevant changes. We're starting to spread the load among @iterative/docs members + @dberenbaum 😬 — the process part is WIP and we're happy to discuss better approaches with the core team.