Fix bump.sh and publish.sh for new crate structure

[clauswilke]

I have added a new crate extendr-engine (#50) to remove the engine part from the default api. However, the scripts bump.sh and publish.sh don't reflect this change yet.

[andy-thomason]

Claus has suggested bumping the version right after the publish. This will help us to distinguish versions that are pulled from github.

[clauswilke]

I like the versioning recommendations in the R packages book, which is to add a dev version (e.g., .9000) right after a package has been published, and then bump to the next non-dev version upon release. Is this possible with the Rust versioning system?

[clauswilke]

I think in Rust we have to go 0.1.10 -> 0.1.11-alpha -> 0.1.11 instead of 0.1.10 -> 0.1.10.9000 -> 0.1.11.

https://docs.rs/semver/0.11.0/semver/

[clauswilke]

Or maybe we should just delete these two scripts and transition to cargo workspaces:
https://crates.io/crates/cargo-workspaces

cargo workspaces version can bump versions.

cargo workspaces publish can publish to crates.io.

[yutannihilation]

cargo workspaces version can bump versions.

Sorry, I forgot to comment that this doesn't handle the versions specified with path. So we need some tweaks about these lines:

extendr/extendr-api/Cargo.toml

Lines 13 to 14 in 4177272

	extendr-macros = { path = "../extendr-macros", version="0.1.11" }
	extendr-engine = { path = "../extendr-engine", version="0.1.11" }

Btw, be careful when you try this command as this immediately commits and pushes the new version to remotes... When I tried this, I wasn't the member of extendr so the attempt was just rejected... --no-git-commit seems to save us.

[clauswilke]

If you have some experience with this tool, could you write up a workflow and add to the README, where it currently talks about bump.sh and publish.sh?

[yutannihilation]

After experimenting a bit more, I think cargo workspaces version is currently broken. I'll try to fix it there, but I'm not sure if it gets done before the next release.

[yutannihilation]

Sorry, it turned out it's just I didn't understand the usage... I think I can write up a workflow soon.