Becoming Stable

[mara-schulke]

This is a open discussion on the features (to be implemented), issues / bugs (that have to be fixed), decisions to be made etc. until we can consider Buffrs to be stable enough for public usage, and longterm support cycles.

Currently as we are pre-1.0 – breaking changes still occur and are done so on purpose to reduce technical debt. Soon enough we will be unable to do this, so writing up a list of breaking changes we need to make now is the first step to improve stability and foster the usage of Buffrs as a platform.

---

Features

• Support OCI registries to become selfhotable
  • Allow use of an OCI Registry instead/alongside of buffrs registry #229
• Dynamic Version Resolution Using Semver + Pubgrub
  • Implement dependency specification resolution #205
  • Implement version resolution #234
  • Refactor the registry system #235
• Cross-Registry Dependencies / Distributed Package Management
• Git Dependencies
  • Support for git dependencies #73
• Local Filesystem Dependencies
• SSO Registry Authentication
  • Figure out auth incl. enterprise compat #16
• Introducing Manifest and Lockfile editions

Housekeeping

• Issue Templates
• Contributing Notice
• PM Setup in GitHub
• Really Good Documentation and Learning Resources

Integrations

• Nix
• Rust / Cargo
  • buffrs::build should be resilient to non-existent credentials #54
  • Remove buffrs::Language as param from buffrs::build #43
  • Disable buffrs::build installing dependencies if we are doing a release build  #55
• Python / Poetry
  • Work on python + js build tool support #27
• JS / TS

Security

• Credential Storage
  • Credentials storage XDG #109
  • Securing The Credential Storage Implementation #119

Datamodel

• Standardizing The Buffrs Package Format

[qsantos]

Regarding the first point, I have taken the liberty of opening #205.