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

Versioning #220

Open
7 tasks
bladyjoker opened this issue May 29, 2024 · 0 comments
Open
7 tasks

Versioning #220

bladyjoker opened this issue May 29, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@bladyjoker
Copy link
Collaborator

bladyjoker commented May 29, 2024

LambdaBuffers should adopt a versioning scheme for the lbf schemas, frontend/compiled, codegen modules, runtime libraries, and the Nix packaging tools.

TODO:

  • Settle on a versioning scheme and document it
  • Figure out the versioning strategy for various parts (what changes are safe, compatible with previous versions, and which are breaking etc)
    • LB Frontend, mostly syntax and module system related.
    • LB Compiler, has a Protobuf API, this should be central to this.
    • LB Codegen, has a Protobuf API, this should be central to this, but also the outputted code might affect users too.
    • Runtime libraries for Prelude and Plutus
  • Introduce CHANGELOG

Before we start releasing the tools and publishing packages, we must have this sorted out.

@bladyjoker bladyjoker added the enhancement New feature or request label May 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: Todo
Development

No branches or pull requests

1 participant