prepare 0.16.0 changelog + version

[jdroenner]

• [x ] I agree to follow the project's code of conduct.
• [x ] I added an entry to CHANGES.md if knowledge of this change could be valuable to users.

---

[lnicola]

The whitespace changes break the formatting:

(not that I find this layout great, but at least it's consistent)

And maybe we should publish it as 0.15.1 and yank 0.15.0?

[jdroenner]

0.15.1 vs 0.16.0 is a good question. Since there is a breaking change we should name it 0.16.0. Using 0.15.1 could cause some code to stop compiling but who ever uses that code should change it anyway 😓 I'm open for suggestions what version number to pick.

[lnicola]

I think it's fine if we yank it and publish 0.15.1, but let's just skip to 0.16.0, as it seems that a lot of people don't really like yanking. I had some more planned breaking changes, but version numbers are free :-).

[lnicola]

@bors r+

[lnicola]

bors r+

[bors]

Build succeeded!

The publicly hosted instance of bors-ng is deprecated and will go away soon.

If you want to self-host your own instance, instructions are here.
For more help, visit the forum.

If you want to switch to GitHub's built-in merge queue, visit their help page.

• ci gdal-3.1.3
• ci gdal-3.2.3
• ci gdal-3.3.3
• ci gdal-3.4.3
• ci gdal-3.5.3
• ci gdal-3.6.4
• ci gdal-3.7.0
• ci ubuntu-lts

[lnicola]

@jdroenner would you mind also publishing the new version to crates.io?

[jdroenner]

yes will do. We need to bump gdal-sys to 0.9.1 because we changed the bindgen version. Should we also bump the dependencies for the gdal crate?