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
[WIP] Add release guide for XTable #434
base: main
Are you sure you want to change the base?
Conversation
@@ -22,7 +22,7 @@ | |||
|
|||
<groupId>org.apache.xtable</groupId> | |||
<artifactId>xtable</artifactId> | |||
<name>xtable</name> | |||
<name>incubator-xtable</name> |
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.
Q: Is this required ? The guidelines say it is.
https://incubator.apache.org/guides/releasemanagement.html
The Incubator policies applies two additional constraints to podlings for their releases. They are repeated here for clarity only. - Release artifacts must include incubating in the final file name - Release artifacts must include one of two disclaimers
@@ -0,0 +1,4 @@ | |||
Apache XTable is an effort undergoing incubation at The Apache Software Foundation (ASF). |
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.
Added this based on guidelines mentioned in https://incubator.apache.org/guides/releasemanagement.html
follow [the guide](https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/) to configure | ||
command line access. | ||
|
||
## One-time Setup Instructions |
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.
Setting up GPG keys and other hardware for signing artifacts.
limitations under the License. | ||
--> | ||
|
||
# Introduction |
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.
Intro about what the release process is going to be.
Before your first release, you should perform one-time configuration steps. This will set up your security keys for | ||
signing the release and access to various release repositories. | ||
|
||
To prepare for each release, you should audit the project status in the JIRA issue tracker, and do the necessary |
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.
We don't have a JIRA setup, so should we use Github issues here ?
@@ -0,0 +1,570 @@ | |||
<!-- |
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 have re-used the release guide when hudi was in incubation stage
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=135859726
Important Read
What is the purpose of the pull request
Add the release guide/process for Apache XTable, the guide has been added based on the guidelines provided by Apache.
https://infra.apache.org/release-publishing
https://www.apache.org/legal/release-policy.html
Special guidelines for incubating projects.
https://incubator.apache.org/guides/releasemanagement.html#best-practice
https://infra.apache.org/release-publishing.html#uploading
Brief change log
(for example:)
Verify this pull request
This pull request is a release guide without any test coverage, the guide will be run in a dry-run mode to ensure everything is working as expected before merging the change to main branch.