Next release

[Kijewski]

• feature freeze
• exchange https://github.com/rinja-rs/ and https://github.com/askama-rs/
• Rename rinja into askama #353
• update the readme and the book
• update readthedocs
• update oss-fuzz
• do one or more pre-releases
• ask kind people to try the pre-release
• write a blog post to explain everything (@GuillaumeGomez)
• release askama v0.13.0
• Release rinja v0.3.6+deprecated #344
• Release rinja v0.4.0+deprecated #345
• archive the old askama project, redirecting users here
• (optional) try to help projects to migrate

Am I missing something? Is this the right order?

[GuillaumeGomez]

I'd prefer if instead we simply renamed the repository into askama. After all we're a fork, so we still have askama git history and that will make things simpler since we don't need to migrate issues and PRs.

Also, I need write a blog post about all this. :)

[Kijewski]

Well, I guess it does not matter a lot. I would have liked the other route better, though, regardless if it is more complicated.

[GuillaumeGomez]

Less work for us. :D

[Kijewski]

I don't think there is anything that we need to include the next release, esp. there are no breaking changes I would like to include. @GuillaumeGomez, is there something you would like to include or can we call it a "feature freeze". :)

[GuillaumeGomez]

Sorry didn't see this message. Yes, time for feature freeze!