Release v0.2.0

[notfilippo]

We need to coordinate with a PMC to organise the vote for the first release of this crate. cc @leerho @freakyzoidberg

Since the crate was already released with code from one of my previous repositories (https://github.com/notfilippo/datasketches-rs), we sadly cannot start from a v0.0.1 or v0.1.0.

Since the latest release is v0.1.3 I would argue we should start fresh with a v0.2.0.

I'll create the PR to bump the version in the Cargo.toml file.

[Xuanwo]

v0.2.0 release looks good to me (iceberg also starts with v0.2.0 because it's donated by other contributor too!)

[leerho]

When you say "Release", are you talking about an Apache Release, where the source is first deployed to /dist/dev/as a release candidate, approved by the PMC, and then deployed to /dist/release/?

These directories do not have a folder for /rust/ yet, but I can easily add that.

We have published our release processes for C++ and Java on our website, and I suggest you do the same, so that we document for the community how we do our releases. For example, Java Release Process

[tisonkun]

These directories do not have a folder for /rust/ yet, but I can easily add that.

Yes please create one.

[tisonkun]

... and we shall release crate to crates.io after the ASF source release passed.

Or alternatively, while I'm considering how to make the library earlier accessible on crates.io, it's possible to release a 0.2.0-rc.1 as a preview/to-be-verified version, that still follows ASF release policies but easier for users to verify with normal cargo dependency workflow.

[notfilippo]

When you say "Release", are you talking about an Apache Release

Yes, it's good to make this distinction. I was talking about the general release process including both the Apache Release and the crates.io release.

I can bootstrap a markdown document in the root of the repo (RELEASE.md?) to document the process I have in mind and we can review formally in a PR.

it's possible to release a 0.2.0-rc.1 as a preview/to-be-verified version [..] easier for users to verify with normal cargo dependency workflow.

Totally agree! cc @leerho , what do you think about this?

[notfilippo]

https://crates.io/crates/datasketches/0.2.0-rc.1 is live, from commit 22c30bc. We will need a PMC member to

• Tag the commit
• Create the /dist/dev release
• Start the voting discussion

[tisonkun]

Today I was invited as a new member of the DataSketches PMC. I'm glad to volunteer to coordinate this release and will start the voting thread on dev@datasketches.apache.org soon.

cc @leerho, does this sound good? I think we can directly start with the voting process, and if there are any issues, resolve them and cut a new RC.

We will need a PMC

@notfilippo a PMC means a project management committee, e.g., the DataSketches PMC. In this context you may probably use "a PMC member".

[notfilippo]

Today I was invited as a new member of the DataSketches PMC

Congrats! 🥳 Thanks for taking care of the voting process.

In this context you may probably use "a PMC member".

Thanks, duly noted!

[tisonkun]

We may need a new RC due to #63 this bug (I'm sorry).

I'll try to include #59 as well since it's almost ready.

Both PRs are blocked by CI failure that would be fixed by apache/datasketches-java#711. I'll manage them to cut a new RC asap.

[tisonkun]

Release vote has started at https://lists.apache.org/thread/7floxlp3dr8znpxzckwz38kh8dwxm19j.

The process needs some adjustment. I'll follow them up later.

[tisonkun]

svn mv https://dist.apache.org/repos/dist/dev/datasketches/rust/0.2.0-rc.2 https://dist.apache.org/repos/dist/release/datasketches/rust/0.2.0 -m "Release Apache DataSketches Rust 0.2.0"