Tagging releases on GitHub

[jsha]

While working on a documentation issue, I tried to check out an earlier version of ureq (v1.1.2), but I found that there are no tagged releases in this repo. Would you be willing to start git tag'ing releases? There's some discussion about using git tag for crate releases at https://users.rust-lang.org/t/psa-please-git-tag-your-crates-io-releases/22223/10.

[algesten]

@jsha sure!

At this point, I was going to ask whether we are should cut a new release – so many improvements!

I just invited you as collaborator.

Instead of me asking you what the plan is, it's better you drive as you see fit. When you think we should release, you can make a tag yourself (cargo bump is nice, which can also automatically do the git commit), ping me and I'll publish it.

I'm very happy to discuss and feedback on PRs, so I don't mean I will be any less involved.

[jsha]

Thanks for the trust! I think it's probably time for a new release soon, but there are a few more tweaks I'd like to land first (will file some issues shortly).

My default assumption is that as a collaborator I will send PRs for every change I originate, even e.g. adding a git commit to bump the version in Cargo.toml. Let me know if you'd like me to modify that default.

[algesten]

@jsha Sounds good! Since I've alone in managing releases and ensuring the stability, I've allowed myself to push to master. But I'm totally happy to stop that and originate any change I want as PR as well.

So let's PR version bumps too!

[jsha]

#80 and #81 are the ones I would like to land before the next version bump. Once those are landed, I think the bundle of changes will be a nice overall improvement to the connection pooling capabilities.

[lolgesten]

Very solid improvement!