Closed wgtmac closed 10 months ago
@gszadovszky @Fokko @shangxinli
Could you please take a look?
Thanks for the suggestion! @gszadovszky
PARQUET-2222 has two different commits associated with it. Let me consolidate them.
I just scanned all commits since last release and dropped two kinds of commits:
Should I open a JIRA for commits that do not open a JIRA? But unfortunately the commit message can no longer change.
@wgtmac, When I am doing a release, I usually start with the list commits as you've done. Then update the jira accordingly (usually we miss to set the proper target release). After it is done I use the jira release page, this time it is https://issues.apache.org/jira/projects/PARQUET/versions/12350092. At this time it would already contain all the jiras already in the release and also the ones someone wanted to do for this release. The latter ones should be investigated whether they really got in or not. If not, should we wait for them. At the end we should have only the jiras in under the target version which are really made into the release. Then create the changelog. (At this point the changelog is redundant, but we usually create it anyway.) There is a somewhat useful tool linked at https://parquet.apache.org/docs/contribution-guidelines/releasing/#release-process to convert the jira query result to the required md format.
I don't think we need jiras for the changes got in without them. Though, it might worth listing the updates in the changelog. Maybe under "Tasks"?
I have updated the status of all JIRAs belong to the release. The changelog is updated as well. Please take a look again. Thanks! @gszadovszky
Thanks @mapleFU @Fokko @gszadovszky! I'll merge this.
Hi @gszadovszky @shangxinli @ggershinsky, could you help the vote below? Thanks in advance!
https://lists.apache.org/thread/fdf1zz0f3xzz5zpvo6c811xjswhm1zy6
I just voted
On Fri, Nov 17, 2023 at 7:03 AM Gang Wu @.***> wrote:
Hi @gszadovszky https://github.com/gszadovszky @shangxinli https://github.com/shangxinli @ggershinsky https://github.com/ggershinsky, could you help the vote below? Thanks in advance!
https://lists.apache.org/thread/fdf1zz0f3xzz5zpvo6c811xjswhm1zy6
— Reply to this email directly, view it on GitHub https://github.com/apache/parquet-format/pull/219#issuecomment-1816586577, or unsubscribe https://github.com/notifications/unsubscribe-auth/AHPXKMLJSRV7OLSRIMNIV3DYE54ETAVCNFSM6AAAAAA7L6BY7GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJWGU4DMNJXG4 . You are receiving this because you were mentioned.Message ID: @.***>
-- Xinli Shang
@Fokko Could you invite PMCs you know to help the vote? Thanks!
Thanks @wgtmac for the heads up! Voted.
Thanks @gszadovszky!
Could you help me on the step 3 of the link below? It seems that I don't have the permission. https://parquet.apache.org/docs/contribution-guidelines/releasing/#3-copy-the-release-artifacts-in-svn-into-releases
mkdir parquet
cd parquet
svn co https://dist.apache.org/repos/dist/dev/parquet candidates
svn co https://dist.apache.org/repos/dist/release/parquet releases
cp -r candidates/apache-parquet-format-2.10.0-rc0/ releases/apache-parquet-format-2.10.0
cd releases
svn add apache-parquet-format-2.10.0
svn ci -m "Parquet Format: Add release 2.10.0"
@wgtmac, I've done the steps you've listed. downloads.apache.org and mirrors will probably need some to time to get in sync.
Thank you very much! @gszadovszky
Make sure you have checked all steps below.
Jira
Commits
Documentation