Page History

...

First, we build the source release:

Non-MAC users:

$ RELEASE_VERSION=$RELEASE_VERSION tools/releasing/create_source_release.sh

MAC users:

First, check your tar version by tar --version. If the output is bsdtar , it will create some extra information which cannot be recognized by gnutar . You can download gnutar  to replace system built-in bsdtar , or you can just use argument --no-xattrs , which is more convenient. 

-- find this line in tools/releasing/create_source_release.sh
tar czf ${RELEASE_DIR}/apache-paimon-${RELEASE_VERSION}-src.tgz paimon-${RELEASE_VERSION}

-- add --no-xattrs
tar czf ${RELEASE_DIR}/apache-paimon-${RELEASE_VERSION}-src.tgz --no-xattrs paimon-${RELEASE_VERSION}

Second, use COPYFILE_DISABLE=1 to avoid generate hidden files:

COPYFILE_DISABLE=1

$ RELEASE_VERSION=$RELEASE_VERSION tools/releasing/create_source_release.sh

...

Update website to point to new stable release documentation (for major releases only)

In our website repository repository paimon-website, for major releases we need to update the website to point to the new stable release.

...

• Maven artifacts released and indexed in the Maven Central Repository (usually takes about a day to show up)
• Source & binary distributions available in the release repository of https://dist.apache.org/repos/dist/release/incubator/paimon/
• Dev repository https://dist.apache.org/repos/dist/dev/incubator/paimon/ is empty
• Release tagged in the source code repository
• Website contains links to new release binaries and sources in download page
• For major releases, the front page references the correct new major release version and directs to the correct link

...

Merge the website pull request to list the release. Make sure to regenerate the website as well, as it isn't build automatically. 

Apache mailing lists

Announce on the dev@ mailing list that the release has been finished.

...