[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17011978#comment-17011978 ] ASF GitHub Bot commented on DRILL-7230: --- asfgit commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > Labels: ready-to-commit > Fix For: 1.18.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17010538#comment-17010538 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on issue #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#issuecomment-571978751 I have squashed the commits. @arina-ielchiieva, thanks a lot for the review, it definitely became good only after addressing your comments. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > Labels: ready-to-commit > Fix For: 1.18.0 > > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009743#comment-17009743 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on issue #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#issuecomment-571598120 Looks really good, thanks for creating such detailed instruction. +1 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009100#comment-17009100 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363416297 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. Review comment: Thanks, fixed. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009105#comment-17009105 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363424260 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009102#comment-17009102 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363417007 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009104#comment-17009104 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363416553 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. Review comment: Done This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009106#comment-17009106 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363431205 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009103#comment-17009103 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363416872 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17009101#comment-17009101 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363416441 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. Review comment: Thanks, replaced. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008784#comment-17008784 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363258029 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. Review comment: ```suggestion 4. Enter your Apache password and submit the changes. ``` This is an automated message from the Apache Git Service. To respond to the message,
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008783#comment-17008783 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r36323 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008785#comment-17008785 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363266847 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008782#comment-17008782 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363257977 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. Review comment: ```suggestion 3. Note that you can add more than one SSH key corresponding to multiple machines. ``` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008789#comment-17008789 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363267838 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008787#comment-17008787 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363267275 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008788#comment-17008788 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363267914 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature into the the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +1. `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist`. +2. Update `KEYS` file with required changes. +3. Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"`. +3. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the Apache server by running the following: `sftp @home.apache.org`. +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17008786#comment-17008786 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r363257698 ## File path: docs/dev/Release.md ## @@ -0,0 +1,397 @@ +# Drill Release Process + +1. ## Setup release final cut-off date +1. Start mail thread on Apache Drill dev list. + +Example: + +Subject: +``` +[DISCUSS] Drill 1.17.0 release +``` +Body: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather a list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify the final cut-off date. +4. Before starting the release send a reminder to the dev list that merge into Apache Drill master is forbidden during release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` +2. ## Setup environment: +1. ### SVN +1. Install subversion client (see instructions on http://subversion.apache.org/packages.html#osx for + installing svn on different systems). +2. Check that svn works: +``` +svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist +``` +You also need writable access to Apache SVN. (You need to be a PMC member for this). +2. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure the default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`). +8. Add your key signature into the the `KEYS` file in the Drill sources repo in the project root directory. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. Review comment: ```suggestion Instruction on how to create the key signature is embedded at the beginning of the `KEYS` file. ``` This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17003295#comment-17003295 ] ASF GitHub Bot commented on DRILL-7230: --- arina-ielchiieva commented on issue #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#issuecomment-568910375 Please include info about Docker. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000933#comment-17000933 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r360362371 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release +``` + +Body example: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify final cut-off date. +4. Before starting the release send a reminder to dev list that merge in Apache Drill master is forbidden during + release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` + +2. ## Setup environment: +1. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`) +8. Add your key signature to the `KEYS` file in the Drill sources repo. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature to the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +- `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist` +- Update `KEYS` file with required changes +- Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"` +2. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the apache server by running the following: `sftp @home.apache.org` + +3. ### SVN Review comment: Moved this section above `GPG key` section. Added instruction on how to install the `svn` client. Regarding writable access to `dist.apache.org`, there are no additional things to do for PMC. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000935#comment-17000935 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r360368151 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release +``` + +Body example: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify final cut-off date. +4. Before starting the release send a reminder to dev list that merge in Apache Drill master is forbidden during + release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` + +2. ## Setup environment: +1. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`) +8. Add your key signature to the `KEYS` file in the Drill sources repo. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature to the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +- `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist` +- Update `KEYS` file with required changes +- Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"` +2. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the apache server by running the following: `sftp @home.apache.org` + +3. ### SVN +You also need access to Apache SVN. (You need to be a PMC member for this). +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +http://www.apache.org/dev/publishing-maven-artifacts.html +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +2. For deploying maven artifacts, you must add entries to your `~/.m2/settings.xml` file as described here: +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +3. In order to encrypt the LDAP password, see here:
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000934#comment-17000934 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r360366168 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release +``` + +Body example: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify final cut-off date. +4. Before starting the release send a reminder to dev list that merge in Apache Drill master is forbidden during + release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` + +2. ## Setup environment: +1. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`) +8. Add your key signature to the `KEYS` file in the Drill sources repo. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature to the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +- `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist` +- Update `KEYS` file with required changes +- Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"` +2. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the apache server by running the following: `sftp @home.apache.org` + +3. ### SVN +You also need access to Apache SVN. (You need to be a PMC member for this). +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +http://www.apache.org/dev/publishing-maven-artifacts.html +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +2. For deploying maven artifacts, you must add entries to your `~/.m2/settings.xml` file as described here: +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +3. In order to encrypt the LDAP password, see here:
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000932#comment-17000932 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r359998793 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release Review comment: Thanks, done. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000936#comment-17000936 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r360362502 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release +``` + +Body example: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify final cut-off date. +4. Before starting the release send a reminder to dev list that merge in Apache Drill master is forbidden during + release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` + +2. ## Setup environment: +1. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`) +8. Add your key signature to the `KEYS` file in the Drill sources repo. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature to the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +- `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist` +- Update `KEYS` file with required changes +- Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"` +2. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the apache server by running the following: `sftp @home.apache.org` + +3. ### SVN +You also need access to Apache SVN. (You need to be a PMC member for this). +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +http://www.apache.org/dev/publishing-maven-artifacts.html +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +2. For deploying maven artifacts, you must add entries to your `~/.m2/settings.xml` file as described here: +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +3. In order to encrypt the LDAP password, see here:
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000931#comment-17000931 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r35029 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release +``` + +Body example: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify final cut-off date. +4. Before starting the release send a reminder to dev list that merge in Apache Drill master is forbidden during + release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` + +2. ## Setup environment: +1. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`) +8. Add your key signature to the `KEYS` file in the Drill sources repo. Review comment: Good point, I have added additional info. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000937#comment-17000937 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937#discussion_r360404569 ## File path: docs/dev/Release.md ## @@ -0,0 +1,365 @@ +# Drill Release Process + +1. ## Setup release final cut-off date + +1. Start mail thread on Apache dev list with the subject: +``` + [DISCUSS] Drill 1.17.0 release +``` + +Body example: +``` +Hi Drillers, + +It's been several months since the last release and it is time to do the next one. I am volunteering to be the release manager. + +If there are any issues on which work is in progress, that you feel we *must* include in the release, please post in reply to this thread. Based on your input we'll define release cut off date. + +Kind regards + +Thanks +``` +2. Gather list of Jiras that need to be included in the release, discuss possible blockers. +3. Identify final cut-off date. +4. Before starting the release send a reminder to dev list that merge in Apache Drill master is forbidden during + release. + +Example: +``` +Note for the committers: +until the release is not over and Drill version is not changed to 1.17.0-SNAPSHOT, please do not push any +changes into Drill master. +``` + +2. ## Setup environment: +1. ### GPG key: +You will need a GPG key set up. This key is needed for signing the release. +1. Read [Apache docs for release signing](http://www.apache.org/dev/release-signing.html). +2. Install the `gpg2` package on Ubuntu, or `gnupg` on MacOS. +3. Generate GPG key using the **Apache email address** if it wasn't done before: +1. Run `gpg --gen-key` and follow the instructions. +2. Remember your passphrase. +3. Save your key pair: +``` + gpg --output mygpgkey_pub.gpg --armor --export MY_KEY_ID + gpg --output mygpgkey_sec.gpg --armor --export-secret-key MY_KEY_ID + ``` +4. Or import existing GPG key pair if required: +``` +gpg --import mygpgkey_pub.gpg +gpg --allow-secret-key-import --import mygpgkey_sec.gpg +``` +5. Have another committer signed your key (add to the trust chain). +Apache advises to do it at +[key signing parties](https://www.apache.org/dev/release-signing.html#key-signing-party). +6. Make sure default key is the key generated using the Apache email. +7. Publish your public key to a public server (e.g. http://pgp.surfnet.nl or http://pgp.mit.edu) +using Web-UIs or CLI (for example using the following command: +`gpg --keyserver hkp://pool.sks-keyservers.net --trust-model always --send-keys`) +8. Add your key signature to the `KEYS` file in the Drill sources repo. +Instruction on how to create the key signature is embedded at the beginning of the KEYS file. +9. Add your key signature to the `KEYS` file in `https://dist.apache.org` (PMC permissions required for this): +- `svn co https://dist.apache.org/repos/dist/release/drill ~/src/release/drill-dist` +- Update `KEYS` file with required changes +- Commit changes: `svn ci -m "Add FirstName LastName's key to KEYS file"` +2. ### Setting up LDAP credentials +1. Go to http://id.apache.org and log in using your Apache login and password. +2. Scroll to the bottom to the 'SSH Key' entry and add the SSH key from your `~/.ssh/id_rsa.pub` file. +If you don't have the SSH key, you should generate it by running `ssh-keygen`. +3. Note that you can add more than 1 SSH key corresponding to multiple machines. +4. Enter your Apache password and submit changes. +5. Verify that you can do an sftp to the apache server by running the following: `sftp @home.apache.org` + +3. ### SVN +You also need access to Apache SVN. (You need to be a PMC member for this). +4. ### Setup Maven +1. Apache's Maven repository access is documented here: +http://www.apache.org/dev/publishing-maven-artifacts.html +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +2. For deploying maven artifacts, you must add entries to your `~/.m2/settings.xml` file as described here: +http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env. +3. In order to encrypt the LDAP password, see here:
[jira] [Commented] (DRILL-7230) Add README.md with instructions for release
[ https://issues.apache.org/jira/browse/DRILL-7230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17000113#comment-17000113 ] ASF GitHub Bot commented on DRILL-7230: --- vvysotskyi commented on pull request #1937: DRILL-7230: Add README.md with instructions for release and release scripts URL: https://github.com/apache/drill/pull/1937 Jira - [DRILL-7230](https://issues.apache.org/jira/browse/DRILL-7230). Release instruction and scripts are based on the https://github.com/parthchandra/drill/wiki/Drill-Release-Process, https://github.com/parthchandra/stuff/blob/master/scripts/drill-release.sh, and https://github.com/parthchandra/stuff/blob/master/scripts/checksum.sh. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Add README.md with instructions for release > --- > > Key: DRILL-7230 > URL: https://issues.apache.org/jira/browse/DRILL-7230 > Project: Apache Drill > Issue Type: Sub-task > Components: Tools, Build Test >Reporter: Sorabh Hamirwasia >Assignee: Vova Vysotskyi >Priority: Major > -- This message was sent by Atlassian Jira (v8.3.4#803005)
