I’d say we should have the release candidate in 2-...
# pinot-dev
v
I’d say we should have the release candidate in 2-3 days. So a week after that for the release if all goes well.
👍 1
r
Thanks for this information. The reason I’m asking is because I’m in the process of re-testing the latest 1.1 snapshot. I discovered some issues in an older 1.1 snapshot that have been resolved.
Could you please share some details on how the whole release process works? For example, how is a release candidate selected? How is the release candidate verified?
You can look at the commits included in this 1.1.0 release in this branch - https://github.com/apache/pinot/tree/release-1.1.0-rc
r
Do the builds from this branch get published to dockerhub?
v
I’m not sure. I’ll have to check and get back.
r
I don't see them in dockerhub
I'm assuming all of the images tagged
1.1.0-SNAPSHOT*
are from master
If the release candidate was published to dockerhub it would make it easier for me to test it in my environment
v
I’m still building the release candidate.
I’ll ping here once done.
👍 1
r
Is it too late to add a small improvement to the release? I have an open PR against master that has been reviewed.
v
Yes. I’ve cut the RC candidate already and sent it out for voting. Looks like this is not a blocker for the release? Can you confirm?
r
It’s not a blocker because I’ve confirmed that the issue can be avoided with a config change and a tradeoff that favors successful task completion over efficient storage usage.
👍 1