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

Minimal Baskets/Regen Ledger 3.0 #732

Closed
67 of 68 tasks
aaronc opened this issue Feb 9, 2022 · 2 comments · Fixed by #811
Closed
67 of 68 tasks

Minimal Baskets/Regen Ledger 3.0 #732

aaronc opened this issue Feb 9, 2022 · 2 comments · Fixed by #811

Comments

@aaronc
Copy link
Member

aaronc commented Feb 9, 2022

Guidelines:

  • one PR with unit tests per checklist item!
  • all PRs against release/v3.0.x unless otherwise noted
  • please put your name next to the checkbox item or issue you're tackling and also communicate on discord
  • let's keep these small with isolated unit tests so there's a quick turn-around (< 1 day) on each item
  • feel free to open multiple PRs for separate items, but review other people's PRs before you start a new one
  • to keep momentum, we pass off PRs that we don't have the bandwidth to finish quickly

BLOCKERS

  • does MsgCreate ValidateBasic needs fee validation? (only check for valid Coins.Validate() which accepts empty coins)
  • add validation & construction for credit class name & basket denom

Todo

Beta Blocking

RC Blocking

QA


Nice to Have/Post Release

@ryanchristo ryanchristo pinned this issue Feb 9, 2022
@aaronc aaronc changed the title Minimal Baskets/Regen Ledger 2.1 Minimal Baskets/Regen Ledger 2.2 Feb 9, 2022
@aaronc aaronc added this to the v2.2 Minimal Baskets milestone Feb 10, 2022
@clevinson clevinson changed the title Minimal Baskets/Regen Ledger 2.2 Minimal Baskets/Regen Ledger 3.0 Feb 16, 2022
@blushi blushi mentioned this issue Feb 17, 2022
19 tasks
@ryanchristo ryanchristo unpinned this issue Mar 2, 2022
@aaronc
Copy link
Member Author

aaronc commented Mar 3, 2022

Okay to close this? Should we move the follow-ups to separate issues? Are they getting tracked and addressed?

@ryanchristo
Copy link
Member

ryanchristo commented Mar 4, 2022

Okay to close this? Should we move the follow-ups to separate issues? Are they getting tracked and addressed?

Follow-ups added as separate issues and being tracked as part of the v4.0 upgrade. Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants