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

Cadence Technical Foundations #3595

Open
21 of 27 tasks
Tracked by #3623
j1010001 opened this issue Sep 27, 2024 · 0 comments
Open
21 of 27 tasks
Tracked by #3623

Cadence Technical Foundations #3595

j1010001 opened this issue Sep 27, 2024 · 0 comments
Assignees
Labels

Comments

@j1010001
Copy link
Member

j1010001 commented Sep 27, 2024

Why (Objective)

High-quality technical foundations (well designed, clear code with no tech-debt, bugs & workarounds) is more efficient to build on and less prone to unintended behaviour leading to errors.

Aside from technical debt, we also had to pause FLIPs. It puts us in a bad light if we ask the community for input, but then let proposals get stale, some are years (!) old. We should be good citizens in the community.

We also have a number of bugs in the codebase. Features sometimes do not work as intended. This leads to frustration of developers, and might even block them from implementing their use case. Worst case the bugs are security issues.

It is essential to deal with those issues before we make further changes to Cadence.

How will we measure success (Key Results) ?

  1. Completing the Bugs & tech-debt task-lists.
  2. Automation to detect breaking changes in Cadence pre-release is updated to cover all relevant onflow repos.
  3. No open Flips from past years. At the start of the cycle, there are [7]

Bugs

Infrastructure to ensure backward-compatibility

  1. Chore

Tech-Debt

  1. Feedback Technical Debt
  2. Technical Debt Testing
    turbolent
  3. Technical Debt Testing
    SupunS
  4. Feedback Technical Debt
  5. Feedback Technical Debt
    SupunS
  6. Technical Debt
    turbolent
  7. Tech Debt
  8. Technical Debt
    SupunS
  9. Documentation Technical Debt
    fxamacker
  10. Technical Debt
    turbolent
  11. Technical Debt
    turbolent
  12. Technical Debt
    turbolent
  13. Technical Debt
    turbolent
  14. Technical Debt
    turbolent

Clean-up open Flips

  1. 7 of 8
    turbolent
  2. Feature Feedback

Stretch goals

  1. Feature Technical Debt
  2. Feature Feedback Technical Debt
  3. Technical Debt
@j1010001 j1010001 changed the title Foundation Technical Foundations Oct 1, 2024
@j1010001 j1010001 added the Epic label Oct 1, 2024
@j1010001 j1010001 changed the title Technical Foundations Cadence Technical Foundations Oct 10, 2024
@j1010001 j1010001 self-assigned this Oct 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants