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

Plutarch 1.2 #315

Closed
L-as opened this issue Feb 21, 2022 · 5 comments · Fixed by #317
Closed

Plutarch 1.2 #315

L-as opened this issue Feb 21, 2022 · 5 comments · Fixed by #317

Comments

@L-as
Copy link
Member

L-as commented Feb 21, 2022

Minor update because of #314 , new Plutus breaks a lot of things. How should we do this?

@srid
@TotallyNotChase
@t1lde
@blamario
@emiflake
(sorry for the ones whom I forgot)

@srid
Copy link
Member

srid commented Feb 21, 2022

new Plutus breaks a lot of things

Are these visible to users of Plutarch (aside from differing benchmarks)?

@L-as
Copy link
Member Author

L-as commented Feb 21, 2022 via email

@TotallyNotChase
Copy link
Collaborator

Well, we should perhaps switch to staging workflow if we have breaking changes right now but still have issues to fix. If everything can be fixed with one PR, then I'm all for merging to master, drafting up the changelog and just releasing.

Can we please have a list of the issues that need tackling for this release?

@L-as
Copy link
Member Author

L-as commented Feb 22, 2022

I agree with that. Let's switch to that.

@L-as L-as pinned this issue Feb 22, 2022
@L-as L-as linked a pull request Feb 24, 2022 that will close this issue
@L-as
Copy link
Member Author

L-as commented Feb 24, 2022

We need to fix #331

@L-as L-as removed a link to a pull request Apr 19, 2022
@L-as L-as linked a pull request Apr 19, 2022 that will close this issue
@L-as L-as closed this as completed in #317 Aug 1, 2022
@TotallyNotChase TotallyNotChase unpinned this issue Aug 12, 2022
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.

3 participants