Is 55.2.0 an RC or actually released? 🤔

[rtyler]

#7394 is the discussion about an RC and creating the release of 55.2.0 but there is already a tag and marked release here for 55.2.0 😖

I am mostly confused because I watch the repo for release updates and saw the new non-RC release but didn't see it on crates.io 🤷

[alamb]

The current 55.2.0 tag is an RC

It isn't an "official apache release" until we approve it and push to crates.io

Maybe the automation added by @kou in #7042 is generating the github releases

Perhaps we need to update the release process so we push tags like 55.2.0-rc1 ,etc and then only push the 0.55.2 tag as part of the post-release process 🤔

[kou]

Oh, sorry.
I misunderstood the apache/arrow-rs release process.
I thought that we tag X.Y.Z-rcN for RC (before vote) and we tag X.Y.Z for release (after vote).

If using X.Y.Z-rcN tag is OK for apache/arrow-rs, I can open pull request(s) that prepares release scripts for the workflow.

[alamb]

I misunderstood the apache/arrow-rs release process.
I thought that we tag X.Y.Z-rcN for RC (before vote) and we tag X.Y.Z for release (after vote).

I think this is what we do in Datafusion and it makes more sense

I will update the release instructions to reflect that process

[alamb]

PR:

• Update release instructions to not push tags until release is approved #7754