| <rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Apache Dubbo – Committer Guide</title><link>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/</link><description>Recent content in Committer Guide on Apache Dubbo</description><generator>Hugo -- gohugo.io</generator><language>en</language><atom:link href="https://dubbo.apache.org/en/docs/contribution-guidelines/committer/index.xml" rel="self" type="application/rss+xml"/><item><title>Docs: Apache Committer Guide</title><link>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/new-committer-guide_dev/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/new-committer-guide_dev/</guid><description> |
| <h2 id="first-how-to-become-a-committer">First: How to become a committer</h2> |
| <h3 id="initial-committers-at-the-project-incubator-stage">Initial committers at the project incubator stage</h3> |
| <p>At the project incubator stage, there will be an initial committers list in the proposal of the incubator project. Confirm that you are one of the initial committers. After the vote is passed in the Apache incubator community, these committers can start preparing their account. See <a href="https://wiki.apache.org/incubator/">incubator wiki</a> for details.</p> |
| <h3 id="the-active-contributor-is-elected-as-a-committer">The active contributor is elected as a committer</h3> |
| <p>At the late development stage, an active contributor can be elected as a committer. See <a href="https://www.apache.org/dev/new-committers-guide.html#becoming-a-committer">how to become a committer</a></p> |
| <h2 id="second-the-individual-contributor-signs-icla">Second: The individual contributor signs ICLA</h2> |
| <h3 id="1-apache-id">1, Apache ID</h3> |
| <p>Choose a Apache ID not in the <a href="http://people.apache.org/committer-index.html">apache committers list page</a>.</p> |
| <h3 id="2-individual-contributor-license-agreement--icla">2, Individual Contributor License Agreement (ICLA):</h3> |
| <p>Download the <a href="https://www.apache.org/licenses/icla.pdf">ICLA template</a>. After filling the icla.pdf with personal information correctly, print, sign, scan, and send it in mail as an attachment to the secretary <a href="mailto:secretary@apache.org">secretary@apache.org</a>, the secretary will help to create the Apache user ID. At the same time, a <a href="mailto:your-id@apache.org">your-id@apache.org</a> mailbox will be created. You can see if the user has been created on the [apache committers list page (http://people.apache.org/committer-index.html).</p> |
| <h2 id="third-join-the-apache-developer-group">Third: Join The Apache Developer Group</h2> |
| <ul> |
| <li> |
| <p>1, login via the <a href="https://id.apache.org/">Apache account tool</a>, when you login at the first time, you can select the &ldquo;Change password?&rdquo; checkbox to get the initial password. Then the initial password will be sent to the forward mailbox (the developer mail recorded in the project incubator proposal)</p> |
| </li> |
| <li> |
| <p>2, about Apache mailbox: does not have its own mail content storage server. It needs to borrow the mail content storage and mail sending functions of other mail providers. In many voting sessions, Apache mailbox is recommended.</p> |
| </li> |
| </ul> |
| <p>There is a question about how to configure the apache.org mailbox forwarding function using other mailboxes.</p> |
| <ol> |
| <li> |
| <p>inbox: to receive mails that sent to <a href="mailto:youer-id@apache.org">youer-id@apache.org</a> mailbox. The forward mailbox configured in the Apache account tool in the first step can use the forward mailbox to pick up incoming mail.</p> |
| </li> |
| <li> |
| <p>the Outbox: emails sent out will show the sender as <a href="mailto:your-id@apache.org">your-id@apache.org</a> account. Please refer to: <a href="https://reference.apache.org/committer/email">set up Apache mailbox guide</a> and <a href="http://gmailblog.blogspot.com/2009/07/send-mail-from-another-address-without.html">Gmail mailbox setting</a>. In other mailbox service settings, this forwarding mode is not easy to find. Gmail is the most convenient, which is recommended (no advertising).</p> |
| </li> |
| </ol> |
| <ul> |
| <li> |
| <p>3, Modify the homepage URL option in the edit page, homepage link of your account can be added in <a href="http://people.apache.org/committer-index.html">apache committer index page</a></p> |
| </li> |
| <li> |
| <p>4, Modify the GitHub account in the edit page, and an email will be sent to invite you to join the github.com/apache-commiiters group. Now, please learn from the way <a href="http://www.apache.org/foundation/how-it-works.html#developers">ASF works</a> to do some basic preparation of ASF development.</p> |
| </li> |
| </ul> |
| <h2 id="fourth-to-obtain-write-permission-of-the-project">Fourth: To obtain write permission of the project</h2> |
| <p>Operation of the <a href="https://gitbox.apache.org/setup/">GitBox account link tool</a></p> |
| <h3 id="1-apache-account-authorization">1, Apache account authorization</h3> |
| <p>According to the prompt, the OAuth protocol of Apache account is authorized to login.</p> |
| <h3 id="2-github-account-authorization">2, Github account authorization</h3> |
| <p>According to the prompt, the OAuth protocol of Github account is authorized to login.</p> |
| <h3 id="3-set-up-github-account-in-githubcom-two-factors-authorization-2fa">3, Set up GitHub account in github.com, two-factors authorization (2FA)</h3> |
| <ul> |
| <li> |
| <ol> |
| <li>install &ldquo;Google Authenticator&rdquo; app on your cell phone</li> |
| </ol> |
| </li> |
| <li>2), Following the <a href="https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication">authorized GitHub 2FA wiki</a>, you can operation step by step .</li> |
| </ul> |
| <p>In the <a href="https://github.com/settings/security">two-factors authorization authentication (2. Scan this barcode with your app.)</a> page, it is not recommended to select a two-dimensional code with a cell phone, because some of the cell phones will not be able to scan.</p> |
| <p>Please open the cell phone &ldquo;Google Authenticator&rdquo; app, click &ldquo;+&rdquo; to select &ldquo;input the secret key&rdquo;: write the GitHub account in the account name input box. In your &ldquo;secret key&rdquo; input box, write the text of the &ldquo;enter this text code&rdquo; link in the open web page. After clicking &ldquo;add&rdquo; in app, 6 digit dynamic will be generated for this account. Write the 6 digit number to the text box in the web page, and then click &ldquo;Enable&rdquo;. In this way, the 2fa is set successfully.</p> |
| <ul> |
| <li> |
| <p>3), logout and login to Github again, and one more step will appear after entering user name and password. Fill in the 6 digit number dynamic password generated by the app</p> |
| </li> |
| <li> |
| <p>4),It will take about half an hour, and you will be notified by mail that you have joined the XX project-committers developer group. You can also check it in the [apache teams] (<a href="https://github.com/orgs/apache/teams">https://github.com/orgs/apache/teams</a>) page yourself.</p> |
| </li> |
| <li> |
| <p>5), After the 2fa has been submitted, you will have the permission check problem for the cloned projects. The solution is one of below two:</p> |
| </li> |
| <li> |
| <p>A. Apply for Access Token</p> |
| </li> |
| </ul> |
| <p>When access token is generated on GitHub, the token where the instruction line needs a password is pasted.</p> |
| <p>Refer to website <a href="https://docs.github.com/en/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors">referenced link one</a> and <a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token">referenced link two</a></p> |
| <ul> |
| <li>B. switch to SSH</li> |
| </ul> |
| <p>ssh-keygen then paste the content in the pub file into GitHub.</p> |
| <p><strong>Note</strong>: ensure that GitHub&rsquo;s 2fa is &ldquo;enabled&rdquo;. When you set 2fa to &ldquo;off&rdquo;, it will be delisted by the corresponding Apache committer write permission group until you set it up again.</p> |
| <h2 id="fifth-other">Fifth: other</h2> |
| <h3 id="the-apache-way">The Apache way</h3> |
| <p>See <a href="http://apache.org/foundation/governance/">wiki</a>.</p> |
| <p>The community is more important than the code |
| If not discussed in the community (mailing list), just as it did not happen.</p> |
| <h3 id="add-your-name">Add your name</h3> |
| <p>Please update Dubbo incubator status <a href="https://incubator.apache.org/projects/dubbo.html">page</a> to add your name. See this <a href="https://dubbo.apache.org/en/latest/contribution-guidelines/contributor/">guide</a> for instructions.</p> |
| <p>Please update Dubbo official <a href="https://dubbo.apache.org/en/latest/contribution-guidelines/committer">website</a> to update your name.</p> |
| <h3 id="a-small-benefit">A small benefit</h3> |
| <p>Jetbrains company gives Apache committers a small benefit, which is free to use IDEA&rsquo;s full series products. The specific address is: <a href="https://www.jetbrains.com/shop/eform/apache?Product=ALL">https://www.jetbrains.com/shop/eform/apache?Product=ALL</a></p> |
| <h3 id="reference-wiki">Reference wiki</h3> |
| <p><a href="https://www.apache.org/dev/new-committers-guide.html">https://www.apache.org/dev/new-committers-guide.html</a></p></description></item><item><title>Docs: Release Guide</title><link>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/release-guide_dev/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/release-guide_dev/</guid><description> |
| <h2 id="understanding-the-apache-release-cycle">Understanding the Apache Release Cycle</h2> |
| <p>In general, Source Release is the key and the required content of Apache. But Binary Release is optional, Dubbo can choose whether to release binary packages to the Apache repository or to the Maven central repository.</p> |
| <p>Please refer to the following links for more information on ASF&rsquo;s release guide:</p> |
| <ul> |
| <li><a href="http://www.apache.org/dev/release-publishing">Apache Release Guide</a></li> |
| <li><a href="http://www.apache.org/dev/release.html">Apache Release Policy</a></li> |
| <li><a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Maven Release Info</a></li> |
| </ul> |
| <h2 id="preparation-of-local-building-environment">Preparation of Local Building Environment</h2> |
| <p>Mainly including the related preparation of signature utilities and Maven repository certification</p> |
| <ol> |
| <li> |
| <p>Install GPG,refer to <a href="https://www.gnupg.org/download/index.html">https://www.gnupg.org/download/index.html</a></p> |
| <ul> |
| <li>For example, in Mac OS</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span>$ brew install gpg |
| </span></span><span style="display:flex;"><span>$ gpg --version <span style="color:#586e75">#check version,should be 2.x</span> |
| </span></span></code></pre></div></li> |
| <li> |
| <p>Generate the key with GPG</p> |
| <ul> |
| <li>Generate the key according to the prompt</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ gpg2 --full-gen-key |
| </span></span><span style="display:flex;"><span>gpg <span style="color:#719e07">(</span>GnuPG<span style="color:#719e07">)</span> 2.0.12; Copyright <span style="color:#719e07">(</span>C<span style="color:#719e07">)</span> <span style="color:#2aa198">2009</span> Free Software Foundation, Inc. |
| </span></span><span style="display:flex;"><span>This is free software: you are free to change and redistribute it. |
| </span></span><span style="display:flex;"><span>There is NO WARRANTY, to the extent permitted by law. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Please <span style="color:#719e07">select</span> what kind of key you want: |
| </span></span><span style="display:flex;"><span> <span style="color:#719e07">(</span>1<span style="color:#719e07">)</span> RSA and RSA <span style="color:#719e07">(</span>default<span style="color:#719e07">)</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#719e07">(</span>2<span style="color:#719e07">)</span> DSA and Elgamal |
| </span></span><span style="display:flex;"><span> <span style="color:#719e07">(</span>3<span style="color:#719e07">)</span> DSA <span style="color:#719e07">(</span>sign only<span style="color:#719e07">)</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#719e07">(</span>4<span style="color:#719e07">)</span> RSA <span style="color:#719e07">(</span>sign only<span style="color:#719e07">)</span> |
| </span></span><span style="display:flex;"><span>Your selection? <span style="color:#2aa198">1</span> |
| </span></span><span style="display:flex;"><span>RSA keys may be between <span style="color:#2aa198">1024</span> and <span style="color:#2aa198">4096</span> bits long. |
| </span></span><span style="display:flex;"><span>What keysize <span style="color:#719e07">do</span> you want? <span style="color:#719e07">(</span>2048<span style="color:#719e07">)</span> <span style="color:#2aa198">4096</span> |
| </span></span><span style="display:flex;"><span>Requested keysize is <span style="color:#2aa198">4096</span> bits |
| </span></span><span style="display:flex;"><span>Please specify how long the key should be valid. |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">0</span> <span style="color:#719e07">=</span> key does not expire |
| </span></span><span style="display:flex;"><span> &lt;n&gt; <span style="color:#719e07">=</span> key expires in n days |
| </span></span><span style="display:flex;"><span> &lt;n&gt;w <span style="color:#719e07">=</span> key expires in n weeks |
| </span></span><span style="display:flex;"><span> &lt;n&gt;m <span style="color:#719e07">=</span> key expires in n months |
| </span></span><span style="display:flex;"><span> &lt;n&gt;y <span style="color:#719e07">=</span> key expires in n years |
| </span></span><span style="display:flex;"><span>Key is valid <span style="color:#719e07">for</span>? <span style="color:#719e07">(</span>0<span style="color:#719e07">)</span> |
| </span></span><span style="display:flex;"><span>Key does not expire at all |
| </span></span><span style="display:flex;"><span>Is this correct? <span style="color:#719e07">(</span>y/N<span style="color:#719e07">)</span> y |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>GnuPG needs to construct a user ID to identify your key. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Real name: Robert Burrell Donkin |
| </span></span><span style="display:flex;"><span>Email address: rdonkin@apache.org |
| </span></span><span style="display:flex;"><span>Comment: CODE SIGNING KEY |
| </span></span><span style="display:flex;"><span>You selected this USER-ID: |
| </span></span><span style="display:flex;"><span> <span style="color:#2aa198">&#34;Robert Burrell Donkin (CODE SIGNING KEY) &lt;rdonkin@apache.org&gt;&#34;</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Change <span style="color:#719e07">(</span>N<span style="color:#719e07">)</span>ame, <span style="color:#719e07">(</span>C<span style="color:#719e07">)</span>omment, <span style="color:#719e07">(</span>E<span style="color:#719e07">)</span>mail or <span style="color:#719e07">(</span>O<span style="color:#719e07">)</span>kay/<span style="color:#719e07">(</span>Q<span style="color:#719e07">)</span>uit? O |
| </span></span><span style="display:flex;"><span>You need a Passphrase to protect your secret key. <span style="color:#586e75"># enter the password, which will be used frequently when packaging.</span> |
| </span></span></code></pre></div><ul> |
| <li>View key id</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span>$ gpg --list-keys |
| </span></span><span style="display:flex;"><span>pub rsa4096/28681CB1 2018-04-26 <span style="color:#586e75"># 28681CB1 is the key id</span> |
| </span></span><span style="display:flex;"><span>uid <span style="color:#719e07">[</span>ultimate<span style="color:#719e07">]</span> liujun <span style="color:#719e07">(</span>apache-dubbo<span style="color:#719e07">)</span> &lt;liujun@apache.org&gt; |
| </span></span><span style="display:flex;"><span>sub rsa4096/D3D6984B 2018-04-26 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75">########### Note: Different diaplay for different version.</span> |
| </span></span><span style="display:flex;"><span>$ gpg --list-keys |
| </span></span><span style="display:flex;"><span>pub rsa4096 2018-11-12 <span style="color:#719e07">[</span>SC<span style="color:#719e07">]</span> |
| </span></span><span style="display:flex;"><span> 63AAE9838F4A303E40BAF5FEA3A1CA7A5D4A3981 <span style="color:#586e75"># Last 8 character(5D4A3981) as key id，it will be used when send public key to keyserver</span> |
| </span></span><span style="display:flex;"><span>uid <span style="color:#719e07">[</span> 绝对 <span style="color:#719e07">]</span> Victory Cao <span style="color:#719e07">(</span>CODE SIGNING KEY<span style="color:#719e07">)</span> &lt;victory@apache.org&gt; |
| </span></span><span style="display:flex;"><span>sub rsa4096 2018-11-12 <span style="color:#719e07">[</span>E<span style="color:#719e07">]</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># send public key to keyserver via key id </span> |
| </span></span><span style="display:flex;"><span>$ gpg --keyserver pgpkeys.mit.edu --send-key 28681CB1 |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># Here pgpkeys.mit.edu is a random selection of keyserver. Any key server from the list https://sks-keyservers.net/status/ is acceptable because they are automatically synchronized.</span> |
| </span></span></code></pre></div><ul> |
| <li>If there are multiple public keys，you can set the default key</li> |
| </ul> |
| <p>~/.gnupg/gpg.conf</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span># If you have more than 1 secret key in your keyring, you may want to |
| </span></span><span style="display:flex;"><span># uncomment the following option and set your preferred keyid. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>default-key 28681CB1 |
| </span></span></code></pre></div><ul> |
| <li>If there are multiple public keys, you can also delete unuseful key：</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span><span style="color:#586e75">### Delete the private key first, then delete the public key.</span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>$ gpg --yes --delete-secret-keys shenglicao2@gmail.com <span style="color:#586e75">### indicate email address </span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>$ gpg --delete-keys 1808C6444C781C0AEA0AAD4C4D6A8007D20DB8A4 |
| </span></span></code></pre></div><ul> |
| <li>config your fingerprint.</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span><span style="color:#586e75">### Show fingerprint info：</span> |
| </span></span><span style="display:flex;"><span>$ gpg --fingerprint liujun |
| </span></span><span style="display:flex;"><span>pub rsa4096 2019-10-17 <span style="color:#719e07">[</span>SC<span style="color:#719e07">]</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#2aa198">1376</span> A2FF 67E4 C477 <span style="color:#2aa198">5739</span> 09BD 7DB6 <span style="color:#2aa198">8550</span> D366 E4C0 |
| </span></span><span style="display:flex;"><span>uid <span style="color:#719e07">[</span>ultimate<span style="color:#719e07">]</span> liujun <span style="color:#719e07">(</span>CODE SIGNING KEY<span style="color:#719e07">)</span> &lt;liujun@apache.org&gt; |
| </span></span><span style="display:flex;"><span>sub rsa4096 2019-10-17 <span style="color:#719e07">[</span>E<span style="color:#719e07">]</span> |
| </span></span></code></pre></div><p>Save the fingerprint, as above <code>1376 A2FF 67E4 C477 5739 09BD 7DB6 8550 D366 E4C0</code>, |
| to the field <code>OpenPGP Public Key Primary Fingerprint</code> in you profile page at <a href="https://id.apache.org">https://id.apache.org</a>.</p> |
| </li> |
| <li> |
| <p>Set up Apache central repository.</p> |
| <ul> |
| <li>The parent pom of Dubbo project is apache pom</li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;parent&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;groupId&gt;</span>org.apache<span style="color:#268bd2">&lt;/groupId&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;artifactId&gt;</span>apache<span style="color:#268bd2">&lt;/artifactId&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;version&gt;</span>19<span style="color:#268bd2">&lt;/version&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/parent&gt;</span> |
| </span></span></code></pre></div><ul> |
| <li> |
| <p>Add the following contents to .m2/settings.xml</p> |
| <p>Enter the passwords after |
| encrypting by <a href="http://maven.apache.org/guides/mini/guide-encryption.html">maven-encryption-plugin</a></p> |
| </li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-xml" data-lang="xml"><span style="display:flex;"><span><span style="color:#268bd2">&lt;settings&gt;</span> |
| </span></span><span style="display:flex;"><span>... |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;servers&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- To publish a snapshot of some part of Maven --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;server&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;id&gt;</span>apache.snapshots.https<span style="color:#268bd2">&lt;/id&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;username&gt;</span> <span style="color:#586e75">&lt;!-- YOUR APACHE LDAP USERNAME --&gt;</span> <span style="color:#268bd2">&lt;/username&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;password&gt;</span> <span style="color:#586e75">&lt;!-- YOUR APACHE LDAP PASSWORD (encrypted) --&gt;</span> <span style="color:#268bd2">&lt;/password&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/server&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- To stage a release of some part of Maven --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;server&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;id&gt;</span>apache.releases.https<span style="color:#268bd2">&lt;/id&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;username&gt;</span> <span style="color:#586e75">&lt;!-- YOUR APACHE LDAP USERNAME --&gt;</span> <span style="color:#268bd2">&lt;/username&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;password&gt;</span> <span style="color:#586e75">&lt;!-- YOUR APACHE LDAP PASSWORD (encrypted) --&gt;</span> <span style="color:#268bd2">&lt;/password&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/server&gt;</span> |
| </span></span><span style="display:flex;"><span> ... |
| </span></span><span style="display:flex;"><span> <span style="color:#586e75">&lt;!-- gpg passphrase used when generate key --&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;server&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;id&gt;</span>gpg.passphrase<span style="color:#268bd2">&lt;/id&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;passphrase&gt;</span><span style="color:#586e75">&lt;!-- yourKeyPassword --&gt;</span><span style="color:#268bd2">&lt;/passphrase&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/server&gt;</span> |
| </span></span><span style="display:flex;"><span> <span style="color:#268bd2">&lt;/servers&gt;</span> |
| </span></span><span style="display:flex;"><span><span style="color:#268bd2">&lt;/settings&gt;</span> |
| </span></span></code></pre></div></li> |
| </ol> |
| <h2 id="pack--upload">Pack &amp; Upload</h2> |
| <ol> |
| <li> |
| <p>Pull the new branch from the master branch as the release branch. If you want to release the ${release_version} version now, pull the new branch ${release_version}-release from 2.6.x. Then the |
| modifications and taggings related to ${release_version} Release Candidates are applied to ${release_version}-release branch, and is merged into the master branch after the final release.</p> |
| </li> |
| <li> |
| <p>First of all, verify that the maven component packing, source packing, signature, etc are working properly on the ${release_version}-release branch.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ mvn clean install -Papache-release |
| </span></span><span style="display:flex;"><span>$ mvn deploy |
| </span></span></code></pre></div></li> |
| </ol> |
| <p>This push the snapshot package to the maven central repository.</p> |
| <ol start="3"> |
| <li> |
| <p><del>Release with maven-release-plugin</del> (<code>Deprecated</code>，Skip this step and refer to next step)</p> |
| <ul> |
| <li><del>verify with dryRun</del></li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ mvn release:prepare -Prelease -Darguments<span style="color:#719e07">=</span><span style="color:#2aa198">&#34;-Dmaven.test.skip=true&#34;</span> -DautoVersionSubmodules<span style="color:#719e07">=</span><span style="color:#b58900">true</span> -Dusername<span style="color:#719e07">=</span>YOUR GITHUB ID -DdryRun<span style="color:#719e07">=</span><span style="color:#b58900">true</span> |
| </span></span></code></pre></div><ul> |
| <li><del>After verification, run release:prepare</del></li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ mvn release:clean |
| </span></span><span style="display:flex;"><span>$ mvn release:prepare -Prelease -Darguments<span style="color:#719e07">=</span><span style="color:#2aa198">&#34;-Dmaven.test.skip=true&#34;</span> -DautoVersionSubmodules<span style="color:#719e07">=</span><span style="color:#b58900">true</span> -Dusername<span style="color:#719e07">=</span>YOUR GITHUB ID -DpushChanges<span style="color:#719e07">=</span><span style="color:#b58900">false</span> |
| </span></span></code></pre></div><blockquote> |
| <p>If you are promted to input password for pushing to GitHub (basically including adding new commits and tags), do not input your login password of GitHub. Use <code>Personal access tokens</code> instead. You can go to <a href="https://github.com/settings/profile">https://github.com/settings/profile</a>, click <code>Developer settings</code> -&gt; <code>Personal access tokens</code>, and generate a new token if not. Please refer to this <a href="https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token">guide</a> for more infomation. |
| you need to choose the release artifactId, next artifactId and the release tag, the default tag is dubbo-parent-xxxx, you need to change it to dubbo-xxxx</p> |
| </blockquote> |
| <p>After executing the above commands, you will find that:</p> |
| <ol> |
| <li>source-release.zip and bin-release.zip are generated under dubbo-distribution directory, please unzip it and check the file structure</li> |
| <li><code>-DpushChanges=false</code> tells maven not to push the commits and tags to the remote repostiroy. If not specified, the version tag will be pushed to github repository, you will see a commit called <code>[maven-release-plugin] prepare release dubbo-x.x.x</code> added.</li> |
| <li>The branch version is upgraded to ${release_version+1}-SNAPSHOT automatically. If <code>-DpushChanges=true</code> is specified, the modifications will be pushed to the remote repository, you will see a commit called <code>[maven-release-plugin] prepare for next development iteration</code> added.</li> |
| </ol> |
| <p>If <code>-DpushChanges=false</code> is specified, you will have to manually push the commit to remote repository before go to next step.</p> |
| <ul> |
| <li><del>Run release:perform</del></li> |
| </ul> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ mvn release:perform -Prelease -Darguments<span style="color:#719e07">=</span><span style="color:#2aa198">&#34;-Dmaven.test.skip=true&#34;</span> -DautoVersionSubmodules<span style="color:#719e07">=</span><span style="color:#b58900">true</span> -Dusername<span style="color:#719e07">=</span>YOUR GITHUB ID |
| </span></span></code></pre></div><p>Maven will download the source code from the tag you just pushed, compile it, and deploy to remote maven repsoitry in staging state.</p> |
| </li> |
| </ol> |
| <h3 id="use-mvn-deploy-to-deploy">use <code>mvn deploy</code> to deploy</h3> |
| <blockquote> |
| <p>Requirement：maven 3.5+</p> |
| </blockquote> |
| <p>modify pom version from 2.7.x-SNAPSHOT to 2.7.x . You can search the full-text in the dubbo project.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ mvn clean install -Prelease |
| </span></span><span style="display:flex;"><span>$ mvn deploy -Prelease -DskipTests |
| </span></span></code></pre></div><p>After this, maven will deploy jar to remote maven repsoitry in staging state.</p> |
| <h3 id="note">Note</h3> |
| <blockquote> |
| <p>When you deploy the package into repository, it will be interrupted for network. So you must restart to desploy.<br> |
| The problem is that missing package occurred many times at deploying. So you should check the quantity of package, especially parent package.</p> |
| </blockquote> |
| <h2 id="prepare-apache-release">Prepare Apache Release</h2> |
| <ol> |
| <li> |
| <p>Prepare the svn local environment (Apache hosting the release content of project by svn)</p> |
| </li> |
| <li> |
| <p>Checkout dubbo to local directory</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ svn checkout https://dist.apache.org/repos/dist/dev/dubbo |
| </span></span></code></pre></div><p>Assume that the local directory is <code>~/apache/dubbo</code></p> |
| </li> |
| <li> |
| <p>The current release version is ${release_version}, new directory</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ <span style="color:#b58900">cd</span> ~/apache/dubbo <span style="color:#586e75"># dubbo svn root directory</span> |
| </span></span><span style="display:flex;"><span>$ mkdir <span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span> |
| </span></span></code></pre></div></li> |
| <li> |
| <p>Add public key to <a href="https://dist.apache.org/repos/dist/dev/dubbo/KEYS">KEYS</a> file if you are the first time to be a release manager. KEYS is mainly used to allow people who participate in the voting to be imported locally to verify the correctness of the sign.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ <span style="color:#719e07">(</span>gpg --list-sigs &lt;your name&gt; <span style="color:#719e07">&amp;&amp;</span> gpg --armor --export &lt;your name&gt;<span style="color:#719e07">)</span> &gt;&gt; KEYS |
| </span></span></code></pre></div><p>For more information on how to get your key id, please refer to this <a href="https://docs.github.com/en/authentication/managing-commit-signature-verification/generating-a-new-gpg-key">guide</a></p> |
| </li> |
| <li> |
| <p>Copy the source.zip package from the Dubbo root directory to the svn local repository dubbo/${release_version}</p> |
| </li> |
| <li> |
| <p>Generate sha512 sign</p> |
| <p>For source-release.zip</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ shasum -a <span style="color:#2aa198">512</span> apache-dubbo-<span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span>-source-release.zip &gt;&gt; apache-dubbo-<span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span>-source-release.zip.sha512 |
| </span></span></code></pre></div><p>For bin-release.zip</p> |
| <p>Please add <code>-b</code> paramter when generating sha512 for bin-release.zip, which indicates it is a binary file.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ shasum -b -a <span style="color:#2aa198">512</span> apache-dubbo-<span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span>-bin-release.zip &gt;&gt; apache-dubbo-<span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span>-bin-release.zip.sha512 |
| </span></span></code></pre></div><p>You should generate something like this:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>b8f13d1df6d6c9a1facc72fafc00b2d22bea1e600517c507467d8fca2f776a7a3877101742da53114bfa629ca5b941eb4d9ef989de43f0833e2a794e7ccf5c8a *apache-dubbo-spring-boot-project-2.7.0-bin-release.zip |
| </span></span></code></pre></div><p>Note there is a <code>*</code> sign before the file name.</p> |
| </li> |
| <li> |
| <p>If the binary release is accompanied with the source release. Run the following command in the dubbo-distribution module:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ mvn install |
| </span></span></code></pre></div><p>Go to target directory, copy bin-release.zip and bin-release.zip.asc to svn local repository dubbo/${release_version}, and refer to step 6 to generate sha512 sign.</p> |
| </li> |
| <li> |
| <p>Commit to Apache svn</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-shell" data-lang="shell"><span style="display:flex;"><span>$ svn status |
| </span></span><span style="display:flex;"><span>$ svn commit -m <span style="color:#2aa198">&#39;prepare for ${release_version} RC1&#39;</span> |
| </span></span></code></pre></div></li> |
| <li> |
| <p>Close the maven staging repository</p> |
| <p>This step is required when prepare for a 2.7.0+ release, where package name has been changed to org.apache. Before that, please make sure all the maven artifacts look good. Login to <a href="http://repository.apache.org">http://repository.apache.org</a>, click the <code>Staging repositories</code> on the left bar, search with keyword Dubbo, and you will see a list of repositories. Find the one you just uploaded, and then click the close button in the top area. This will do some sannity check, such as gpg signature check, and checksum check. After that, a link will be shown in the summary tab in the bottom. Please copy that link, it will be used for release vote. The link should look like this: <code>https://repository.apache.org/content/repositories/orgapachedubbo-1015</code>.</p> |
| <blockquote> |
| <p>Please be aware that it may fail when you close the repository, this is normally due to network issues, please try again if it failed. You can confirm it by clicking the <code>Activiey</code> tab next to <code>Summary</code>.</p> |
| </blockquote> |
| </li> |
| </ol> |
| <h2 id="verify-release-candidates">Verify Release Candidates</h2> |
| <p><strong>A full check list can be found <a href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist">here</a></strong></p> |
| <p>The verification link includes but is not limited to the following contents and forms:</p> |
| <h3 id="check-signatures-and-hashes-are-good">Check signatures and hashes are good</h3> |
| <h4 id="check-the-sha512-sum">check the sha512 sum</h4> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span>$ shasum -c apache-dubbo-<span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span>-source-release.zip.sha512 |
| </span></span><span style="display:flex;"><span>$ shasum -c apache-dubbo-<span style="color:#2aa198">${</span><span style="color:#268bd2">release_version</span><span style="color:#2aa198">}</span>-bin-release.zip.sha512 |
| </span></span></code></pre></div><h4 id="check-the-gpg-signarure">check the gpg signarure</h4> |
| <p>If it&rsquo;s your first time verify a release candidte, you should import public keys first.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span> $ curl https://dist.apache.org/repos/dist/dev/dubbo/KEYS &gt;&gt; KEYS <span style="color:#586e75"># download public keys to local directory</span> |
| </span></span><span style="display:flex;"><span> $ gpg --import KEYS <span style="color:#586e75"># import keys</span> |
| </span></span><span style="display:flex;"><span> $ gpg -—edit-key liujun |
| </span></span><span style="display:flex;"><span> &gt; trust <span style="color:#586e75"># type trust command</span> |
| </span></span></code></pre></div><p>Now, you can verify signature with command</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span>gpg --verify apache-dubbo-2.6.3-source-release.zip.asc apache-dubbo-2.6.3-source-release.zip |
| </span></span><span style="display:flex;"><span>gpg --verify apache-dubbo-2.6.3-bin-release.zip.asc apache-dubbo-2.6.3-bin-release.zip |
| </span></span></code></pre></div><h3 id="check-source-release-file-content">Check source release file content</h3> |
| <p>Unzip apache-dubbo-${release_version}-source-release.zip to the default directory and check the following:</p> |
| <ul> |
| <li>DISCLAIMER exists</li> |
| <li>LICENSE and NOTICE exists and contents are good</li> |
| <li>All files and no binary files exist</li> |
| <li>All files has standard ASF License header</li> |
| <li>Can compile from source</li> |
| <li>All unit tests can pass |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span>mvn clean <span style="color:#b58900">test</span> <span style="color:#586e75"># This will run all unit tests</span> |
| </span></span><span style="display:flex;"><span><span style="color:#586e75"># you can also open rat and style plugin to check if every file meets requirements.</span> |
| </span></span><span style="display:flex;"><span>mvn clean <span style="color:#b58900">test</span> -Drat.skip<span style="color:#719e07">=</span><span style="color:#b58900">false</span> -Dcheckstyle.skip<span style="color:#719e07">=</span><span style="color:#b58900">false</span> |
| </span></span></code></pre></div></li> |
| <li>Release candidates match with corresponding tags, you can find tag link and hash in vote email. |
| <ul> |
| <li>check the version number in pom.xml are the same</li> |
| <li>check there are no extra files or directories in the source package, for example, no empty directories or useless log files.<br> |
| <code>diff -r rc_dir tag_dir</code></li> |
| <li>check the top n tag commits, dive into the related files and check if the source package has the same changes</li> |
| </ul> |
| </li> |
| </ul> |
| <h3 id="check-third-party-dependencies">check third party dependencies</h3> |
| <p>According to ASF policy, any <a href="https://www.apache.org/legal/resolved.html#what-can-we-not-include-in-an-asf-project-category-x">Category X</a> dependency can not be included in ASF product, this includes common LGPL/GPL licensed dependencies. Even transitive dependencies are not allowed. Therefore we need to run the following command to ensure no such dependencies are included.</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-sh" data-lang="sh"><span style="display:flex;"><span>mvn license:add-third-party -Dlicense.useMissingFile |
| </span></span><span style="display:flex;"><span>find . -name THIRD-PARTY.txt | xargs grep -E <span style="color:#2aa198">&#39;GPL|General Public License&#39;</span> | grep -v Apache | grep -v MIT | grep -v CDDL |
| </span></span></code></pre></div><p>If one dependency is dual/multiple licensed, just choose the most permissive one.</p> |
| <p>You can refer to this article : <a href="https://apache.org/legal/resolved.html">ASF 3RD PARTY LICENSE POLICY</a></p> |
| <h3 id="check-binary-distribution-file-content">Check binary distribution file content</h3> |
| <p>Unzip apache-dubbo-${release_version}-bin-release.zip and check:</p> |
| <ul> |
| <li>Check signatures are good</li> |
| <li>LICENSE and NOTICE exists and contents are good</li> |
| </ul> |
| <p>Note that if the binary distribution contains third party files, you may need to update LICENSE file by adding the 3rd party license files. If these dependency is Apache License 2.0, and it contains NOTICE file, you may also need to update NOTICE file as well.</p> |
| <h2 id="release-vote">Release vote</h2> |
| <p>The voting just only one round:</p> |
| <p>Dubbo community votes and sends the voting email to <a href="mailto:dev@dubbo.apache.org">dev@dubbo.apache.org</a>. After reviewing by community developers and winning 3 binding tickets that agree to release, you can go to the next stage of voting.</p> |
| <p>The mail template for Apache Dubbo vote：</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-tex" data-lang="tex"><span style="display:flex;"><span>Hello Dubbo Community, |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>This is a call for vote to release Apache Dubbo version 2.7.2. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>The release candidates: |
| </span></span><span style="display:flex;"><span>https://dist.apache.org/repos/dist/dev/dubbo/2.7.2/ |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>The staging repo: |
| </span></span><span style="display:flex;"><span>https://repository.apache.org/content/repositories/orgapachedubbo-1005 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Git tag for the release: |
| </span></span><span style="display:flex;"><span>https://github.com/apache/dubbo/tree/dubbo-2.6.2 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Hash for the release tag: |
| </span></span><span style="display:flex;"><span>afab04c53edab38d52275d2a198ea1aff7a4f41e |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Release Notes: |
| </span></span><span style="display:flex;"><span>https://github.com/apache/dubbo/releases/tag/untagged-4775c0a22c60fca55118 |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>The artifacts have been signed with Key : 28681CB1, which can be found in the keys file: |
| </span></span><span style="display:flex;"><span>https://dist.apache.org/repos/dist/dev/dubbo/KEYS |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>The vote will be open for at least 72 hours or until necessary number of votes are reached. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Please vote accordingly: |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>[ ] +1 approve |
| </span></span><span style="display:flex;"><span>[ ] +0 no opinion |
| </span></span><span style="display:flex;"><span>[ ] -1 disapprove with the reason |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Thanks, |
| </span></span><span style="display:flex;"><span>The Apache Dubbo Team |
| </span></span></code></pre></div><p>The mail template to announce the vote result:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>We’ve received 3 +1 binding votes and one +1 non-binding vote: |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>+1 binding, Ian Luo |
| </span></span><span style="display:flex;"><span>+1 binding, Huxing Zhang |
| </span></span><span style="display:flex;"><span>+1 binding, Jun Liu |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>+1 non-binding, Jerrick |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>I will release this version today. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Best regards, |
| </span></span><span style="display:flex;"><span>The Apache Dubbo Team |
| </span></span></code></pre></div><h2 id="official-release">Official Release</h2> |
| <p>When the release vote has passed,</p> |
| <ol> |
| <li>Add the release files to <a href="https://dist.apache.org/repos/dist/release/dubbo">official release directory</a></li> |
| <li>Remove the release files in <a href="https://dist.apache.org/repos/dist/dev/dubbo">dev directory</a></li> |
| <li>Remove the the release file for the previous release under <a href="https://dist.apache.org/repos/dist/release/dubbo/">official release directory</a>, which will be archived and can be found <a href="https://archive.apache.org/dist/dubbo/">here</a></li> |
| <li>Publish <a href="https://github.com/apache/dubbo/releases">release notes</a> on Github.</li> |
| <li>Update the recommend dependency on <a href="https://github.com/apache/dubbo#maven-dependency">Github</a> to the latest version, also update the version in other place if necessary.</li> |
| <li>Add the download link to official website <a href="https://dubbo.apache.org/en/blog/2020/05/18/past-releases/">https://dubbo.apache.org/en/blog/2020/05/18/past-releases/</a>, using the ASF mirror system. The latest release download link should be something like <a href="https://www.apache.org/dyn/closer.cgi?path=dubbo/$VERSION/apache-dubbo-$VERSION-source-release.zip">this</a>. The download link for the previous release version should be changed like <code>https://archive.apache.org/dist/dubbo/$VERSION/apache-dubbo-$VERSION-bin-release.zip</code>. Please refer to the <a href="https://dubbo.apache.org/en/blog/2020/05/18/past-releases/">download page</a> for more details.</li> |
| <li>Make sure all the commits in the release branch are merged into master branch, and then remove the remote release branch. For example: <code>git push origin --delete 2.7.0-release</code></li> |
| <li>Send mail to <a href="mailto:dev@dubbo.apache.org">dev@dubbo.apache.org</a> , notify the community that the release is completed. |
| The mail template to announce release:</li> |
| </ol> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-text" data-lang="text"><span style="display:flex;"><span>Hello Community, |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>The Apache Dubbo team is pleased to announce that the |
| </span></span><span style="display:flex;"><span>2.6.6 has just been released. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Apache Dubbo™ is a high-performance, java based, open source |
| </span></span><span style="display:flex;"><span>RPC framework. Dubbo offers three key functionalities, which include |
| </span></span><span style="display:flex;"><span>interface based remote call, fault tolerance &amp; load balancing, and |
| </span></span><span style="display:flex;"><span>automatic service registration &amp; discovery. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>Both the source release[1] and the maven binary release[2] are available |
| </span></span><span style="display:flex;"><span>now, you can also find the detailed release notes here[3]. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>If you have any usage questions, or have problems when upgrading or find |
| </span></span><span style="display:flex;"><span>any problems about enhancements included in this release, please don’t |
| </span></span><span style="display:flex;"><span>hesitate to let us know by sending feedback to this mailing list or filing |
| </span></span><span style="display:flex;"><span>an issue on GitHub[4]. |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span> |
| </span></span><span style="display:flex;"><span>[1] https://dubbo.apache.org/en/blog/2020/05/18/past-releases/ |
| </span></span><span style="display:flex;"><span>[2] https://repo1.maven.org/maven2/org/apache/dubbo/dubbo |
| </span></span><span style="display:flex;"><span>[3] https://github.com/apache/dubbo/releases |
| </span></span><span style="display:flex;"><span>[4] https://github.com/apache/dubbo/issues |
| </span></span></code></pre></div><h2 id="complete-maven-convenient-binary-release">Complete Maven Convenient Binary release</h2> |
| <p><strong><a href="https://repository.apache.org/">repository.apache.org</a> The permissions of the nexus repository have been applied, see <a href="https://issues.apache.org/jira/browse/INFRA-16451">jira</a>。</strong></p> |
| <p>To release the maven artifacts, go to <a href="https://repository.apache.org">repository.apache.org</a>, and choose the staging repository, click the release button. Wait for a moment and verify it at <a href="https://repository.apache.org/content/repositories/releases/org/apache/dubbo/">here</a>, make sure your artifacts are there and correct. It will take some time to sync to maven central repository. You can verify it at <a href="https://repo.maven.apache.org/maven2/org/apache/dubbo">here</a></p> |
| <h2 id="faq">FAQ</h2> |
| <h4 id="gpg-signing-failed-inappropriate-ioctl-for-device">gpg: signing failed: Inappropriate ioctl for device</h4> |
| <p>If you&rsquo;ve encountered this error, try the following commands:</p> |
| <div class="highlight"><pre tabindex="0" style="color:#93a1a1;background-color:#002b36;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code class="language-fallback" data-lang="fallback"><span style="display:flex;"><span>export GPG_TTY=$(tty) |
| </span></span></code></pre></div></description></item><item><title>Docs: Label an Issue</title><link>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/label-an-issue-guide_dev/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/label-an-issue-guide_dev/</guid><description> |
| <p>If you are handling an issue, remember to <strong>mark the issue cearly with one or more labels</strong> whenever you think it&rsquo;s meaningful. With labels on, other developers can easily recognize problems, classify them or track progress.</p> |
| <p>For issues or pull requests that need coding and further version release to fix, you should always <strong>mark it with a <a href="https://github.com/apache/dubbo/milestones">milestone</a></strong>.</p> |
| <p>Some frequently used labels:</p> |
| <ul> |
| <li> |
| <p>Help Wanted</p> |
| <ul> |
| <li>help wanted</li> |
| <li>good first issue</li> |
| </ul> |
| </li> |
| <li> |
| <p>Prority</p> |
| <ul> |
| <li>priority/blocker</li> |
| <li>priority/high</li> |
| <li>priority/low</li> |
| <li>priority/normal</li> |
| </ul> |
| </li> |
| <li> |
| <p>Status</p> |
| <ul> |
| <li>status/need-triage</li> |
| <li>status/DO-NOT-MERGE</li> |
| <li>status/READY-TO-MERGE</li> |
| <li>status/invalid</li> |
| <li>status/wontfix</li> |
| </ul> |
| </li> |
| <li> |
| <p>Type</p> |
| <ul> |
| <li>type/bug</li> |
| <li>type/documentation</li> |
| <li>type/enhancement</li> |
| <li>type/feature</li> |
| </ul> |
| </li> |
| </ul></description></item><item><title>Docs: Website Guide</title><link>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/website-guide_dev/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/website-guide_dev/</guid><description> |
| <ol> |
| <li>The website repository of Apache Dubbo is <a href="https://github.com/apache/dubbo-website">https://github.com/apache/dubbo-website</a></li> |
| <li>After building the website, it&rsquo;ll be published to dubbo.apache.org automatically, you can also trigger it manually via <a href="https://selfserve.apache.org">https://selfserve.apache.org</a> (need to login with Apache account)</li> |
| </ol></description></item><item><title>Docs: Apache Official Dubbo Page Maintenance</title><link>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/apache-dubbo-page_dev/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://dubbo.apache.org/en/docs/contribution-guidelines/committer/apache-dubbo-page_dev/</guid><description> |
| <p>Apache has an official website that maintains information about all incubation projects. |
| Each incubation project has an information page under this website. |
| Dubbo&rsquo;s information page address is <a href="https://incubator.apache.org/projects/dubbo.html">https://incubator.apache.org/projects/dubbo.html</a>.</p> |
| <p>When the project has undergone major changes, such as the addition of a new committer, |
| the election of a new PMC, or a new version of Release, etc, these updates need to be maintained on this page. |
| The project address for this official website is |
| <a href="https://svn.apache.org/repos/asf/incubator/public/trunk">https://svn.apache.org/repos/asf/incubator/public/trunk</a>.</p> |
| <p>Here&rsquo;s how to maintain this page:</p> |
| <ol> |
| <li>Install the SVN. If it is a Mac OS X system or a Linux system, it comes with SVN. If it is a Windows system, |
| please install SVN first.</li> |
| <li>Check out the <a href="https://svn.apache.org/repos/asf/incubator/public/trunk">project</a> with SVN.</li> |
| <li>Modify the content/projects/dubbo.xml file and save it.</li> |
| <li>Install ANT. And execute the ant command in the trunk directory to build.</li> |
| <li>After the build is complete, open the target/site/projects/dubbo.html file with your browser to see if the changes take effect.</li> |
| <li>Use the commit command of SVN to submit the dubbo.xml file to the server, and do not submit the dubbo.html file |
| (because the server will automatically build it at regular intervals). |
| This process will ask for the Apache id and password.</li> |
| </ol> |
| <p>References:</p> |
| <ol> |
| <li><a href="http://incubator.apache.org/guides/website.html">http://incubator.apache.org/guides/website.html</a></li> |
| <li><a href="https://svn.apache.org/repos/asf/incubator/public/trunk/README.txt">https://svn.apache.org/repos/asf/incubator/public/trunk/README.txt</a></li> |
| </ol></description></item></channel></rss> |
