A new release and switching the default branch to dev

[konstin]

I'd like to submit this issue as a request to publish a new release, 0.3.0, and to switch the default branch to dev. I believe pubgrub should create new minor releases as its api evolves so downstream crates can easily integrate upstream improvements.

The last release was mid 2021. Since then there were significant changes. These changes are currently not reflected on docs.rs.

The main development of pubgrub happens on the dev branch. When comparing branches and creating PRs, github currently always picks the wrong branch as default (release instead of dev). There should be no problem with the readme since all code examples are on docs.rs and in the book only.

[Eh2406]

We are long overdue for a new release. I feel uncomfortable cutting the release when I still have clear breaking changes in the works, and they just keep coming. In fact, your team has initiated many of the recent requests for breaking changes. :-P

[Eh2406]

Less flippantly, there is a lot of polishing work involved in cutting a release. This is work not strictly required for UV to make progress, but is required to keep this project usable for all comers and maintainable in the long run. I have not been doing good job of focusing on this work. We have https://github.com/pubgrub-rs/pubgrub/milestone/1 to track work in this repo and pubgrub-rs/guide#7 to track updating the guide. If you would like to see the next release, concentrated contributions toward any of that work would be extremely helpful.

[Eh2406]

@mpizenberg Thoughts on changing the branch?

[mpizenberg]

Changing branch sounds good. I agree it's not convenient for people to not have PRs pointing to dev by default. I wish this setup could be split in github. Also if we keep the guide in sync with stable it's also fine if we are careful with what we put and link in the readme.

[Eh2406]

Separate issue made for moving the website. (But entirely supportive of whatever works best.)

Also I change the default branch.