Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3.0 Release Checklist #2869

Closed
8 of 10 tasks
epage opened this issue Oct 13, 2021 · 3 comments
Closed
8 of 10 tasks

3.0 Release Checklist #2869

epage opened this issue Oct 13, 2021 · 3 comments
Labels
A-meta Area: administrative question or tracking issue C-tracking-issue Category: A tracking issue for an unstable feature S-blocked Status: Blocked on something else such as an RFC or other implementation work.
Milestone

Comments

@epage
Copy link
Member

epage commented Oct 13, 2021

  • 1 month of release candidate feedback
  • Double check all docs
    • Match 3.0?
    • Generally, use more specific derive traits than Parser?
    • Good jumping off point for most users
    • Examples use global_settings where possible to raise awareness
  • Double check all examples
  • Double Check readme
  • Double check examples on clap.rs
    • Compile?
  • Changelog
  • Clippy Run (CI)
  • Rustfmt Run (CI)
  • Spell Check Docs
  • Blog Post
@epage epage added A-meta Area: administrative question or tracking issue M: blocked labels Oct 13, 2021
@epage epage added this to the 3.0 milestone Oct 13, 2021
@epage epage mentioned this issue Oct 13, 2021
87 tasks
@pksunkara pksunkara pinned this issue Oct 13, 2021
@wldevries
Copy link

Not sure if this is the right place, but the readme in this repository for "Using Derive Macros" is incorrect at the moment. It uses Parser instead of the replacement type Clap.

@tranzystorekk
Copy link
Contributor

@wldevries According to d840d56 the Clap trait has been renamed to Parser to show what it does more specifically.

@sylvestre
Copy link

Bravo @epage thanks for the hard work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-meta Area: administrative question or tracking issue C-tracking-issue Category: A tracking issue for an unstable feature S-blocked Status: Blocked on something else such as an RFC or other implementation work.
Projects
None yet
Development

No branches or pull requests

5 participants