-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Community] add fury release documentation #109
Conversation
Hi @tisonkun @pjfanning @vesense @PragmaTwice @theweipeng @eolivelli @carp84 I'm not sure whether all the process are correct, I've read all apache release documents and referenced opendal and streampakr. Could you help review this release process? |
6a1d30b
to
cd54246
Compare
### What if vote fail | ||
|
||
If the vote failed, click "Drop" to drop the staging Maven artifacts. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there are some concerns raised from the vote thread, could we update current build artifacts without filing a new vote thread if we don't update the code.
For example, one may forget add signature by accident. Could we continute current vote if the release manager uploaded the signature file and reply in the vote thread
|
||
The svn repository of the release branch is: https://dist.apache.org/repos/dist/release/incubator/fury | ||
|
||
Please add the public key to KEYS in the release branch: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a good idea to do a sparse svn checkout of dist and to do infinite depth on release and staging dirs for fury. I only have my mobile so can't provide detailed setup today. The idea is that dist is huge but you want to be able to svn mv
RCs when the vote passes - from staging to releases.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apologies - should be dev not staging
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see, thanks. This will be much better
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You mean something like this:
svn checkout --depth empty https://dist.apache.org/repos/dist apache-dist
cd apache-dist
svn update --set-depth infinity dev/incubator/fury release/incubator/fury
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will svn mv https://dist.apache.org/repos/dist/dev/incubator/fury/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/fury/${release_version} -m "Release fury ${release_version}"
work directly without pull it to local?
Hi, with two versions released, I think this PR is ready for review |
What this PR do?
This release doc is referenced from opendal and streampark, thanks for their great work.
The website screencut:
Related issue
apache/fury#1421
apache/fury#1389