Thanks for your advice~ I’ve created the key files: - https://dist.apache.org/repos/dist/release/pegasus/KEYS - https://dist.apache.org/repos/dist/dev/pegasus/KEYS <https://dist.apache.org/repos/dist/release/pegasus/KEYS> I will upload the sources and binaries tomorrow. After that, I will formally initiate a vote for this release.
Here below are the commands I used to create the directories of releases. ``` svn mkdir https://dist.apache.org/repos/dist/release/pegasus svn checkout https://dist.apache.org/repos/dist/release/pegasus pegasus-release svn mkdir https://dist.apache.org/repos/dist/dev/pegasus <https://dist.apache.org/repos/dist/release/pegasus> svn checkout https://dist.apache.org/repos/dist/dev/pegasus <https://dist.apache.org/repos/dist/release/pegasus> pegasus-dev ``` BTW, I found a very detailed manual of releasing in ASF policy here: https://beam.apache.org/contribute/release-guide/. That is https://beam.apache.org/contribute/release-guide/#accounts where I followed to create my GPG key. 张铎(Duo Zhang) <[email protected]> 于2020年8月28日周五 下午9:53写道： > I think we need to make use of the resources of ASF for holding the release > sources and binaries. > > https://dist.apache.org/repos/dist/dev/ > > Please create a directory for pegasus here. It is just a SVN repo. This is > the place for placing the RC binaries. > > https://dist.apache.org/repos/dist/release/ > > Please also create a directory for pegasus here. It is for holding the > release binaries. > > And all the tarballs of binaris should have a sha512 checksum file, and > also signed with your key. You should include the public key in the > > https://dist.apache.org/repos/dist/release/pegasus/KEYS > > This is an example for hbase > > https://dist.apache.org/repos/dist/release/hbase/KEYS > > And the order of steps for releasing is wrong... > AFAIK, you should put up a 2.1.0RC0 first(with the release binaries > uploaded to dist dev), and let PPMCs vote. If the vote passes, you can move > the binaries files to dist release, rename it to 2.1.0, and it will be > 2.1.0 release of pegasus. > > And you should also have a download page, like this > https://hbase.apache.org/downloads.html > > And the url of the actual binaries files should be like this: > > https://www.apache.org/dyn/closer.lua/hbase/2.3.1/hbase-2.3.1-bin.tar.gz > > This is for making use of the mirrors of ASF download. The binary files > under dist release will be mirrored to these mirror site to let users > download from the mirrors. > > Thanks. > > Tao Wu <[email protected]> 于2020年8月27日周四 下午6:33写道： > > > Hi, all > > > > We are preparing to release the next version of Pegasus, v2.1.0-rc1. Most > > files in Pegasus are still copyrighted to Xiaomi and not comply with the > > ASF policy. I've added a DISCLAIMER-WIP according to this doc [1] to > state > > that we are working on this. > > > > Because this is the first community version, we are not quite familiar > > with the entire process. Here's my todo, please correct me if anything > I've > > missed: > > > > 1. I will request votes to [email protected]. > > 2. If the vote passes (with at least 3 approvals), I will send a > "[RESULT] > > [VOTE]" summary to [email protected]. > > 3. Then we are able to release v2.1.0-rc1, with: > > - git tag v2.1.0-rc1, identifying the sources of this version. > > - binaries of v2.1.0-rc1 uploaded to github releases [2], including > > pegasus-tools and pegasus-server > > > > [1] > > > > > https://incubator.apache.org/policy/incubation.html#work_in_progress_disclaimer > > [2] https://github.com/apache/incubator-pegasus/releases > > > > After v2.1.0-rc1 is released, we soon will work towards v2.1.0 if no > other > > fixes. > > > > Best regards, > > Wu Tao > > >
