-
Notifications
You must be signed in to change notification settings - Fork 14
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
Ready for v0.3.0? #101
Comments
Actually yes! I wanted to add slice pattern matching before a new release. But that's the only thing I can think of on my side. |
Yes, that can be quite a useful feature, too! I guess the parsing is 99% the same as parsing tuples, except for the delimiters. |
Or do you want to implement |
I suppose the whole |
Should we make the release now (I'll let you make this one 😛)? Gonna work on the |
Will do a release later this evening (CEST). :) |
Yeay! \o/ |
Wow looks nice! I wonder if we could automate that too. XD Anyway, thanks a lot, it's awesome! Announcing on socials. |
When you click on Releases, then on the top-right there is a button "draft new release". There you can select the newest tag, and with "Generate release notes" you get the same output as in my release message. :) Unless I forget it, I check the "Create a discussion for this release" box, so the easier to answer questions or any comments to the release can get consolidated into one page |
Oh nice, thanks for the information! We should put it in a "releasing.md" file to have the list of things we need to do when releasing. |
We have added and changed a lot since the first release. Do you think we are ready for 0.2.1? I think rinja_parser has to get bumped to 0.3.0, because we added removed enum members, but the current HEAD should be compatible to rinja + rinja_derive 0.2.0.
What do you think, @GuillaumeGomez? Do you have something you wish to add or change before we do the next release?
The text was updated successfully, but these errors were encountered: