<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>How to Prepare an Apache Release on Apache Dubbo</title><link>https://deploy-preview-3199--dubbo.netlify.app/en/contact/committer/release-guide/</link><description>Recent content in How to Prepare an Apache Release on Apache Dubbo</description><generator>Hugo</generator><language>en</language><atom:link href="https://deploy-preview-3199--dubbo.netlify.app/en/contact/committer/release-guide/index.xml" rel="self" type="application/rss+xml"/><item><title>General Release Process</title><link>https://deploy-preview-3199--dubbo.netlify.app/en/contact/committer/release-guide/common/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-3199--dubbo.netlify.app/en/contact/committer/release-guide/common/</guid><description>&lt;h2 id="understanding-the-content-and-process-of-apache-releases">Understanding the Content and Process of Apache Releases&lt;/h2>
&lt;p>In general, Source Release is the primary focus of Apache and a necessary element of the release; Binary Release is optional, and Dubbo can choose whether to release binary packages to the Apache repository or publish to the Maven Central Repository.&lt;/p>
&lt;p>Please refer to the following links for more information about the ASF release guidelines:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="http://www.apache.org/dev/release-publishing">Apache Release Guide&lt;/a>&lt;/li>
&lt;li>&lt;a href="http://www.apache.org/dev/release.html">Apache Release Policy&lt;/a>&lt;/li>
&lt;li>&lt;a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Maven Release Info&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="release-process">Release Process&lt;/h2>
&lt;h3 id="1-prepare-a-branch">1. Prepare a Branch&lt;/h3>
&lt;p>Create a new branch from the trunk as a release branch. For example, to release version &lt;code>${release_version}&lt;/code>, create a new branch &lt;code>${release_version}-release&lt;/code> from the development branch. All modifications and tagging related to &lt;code>${release_version}&lt;/code> Release Candidates will then occur in the &lt;code>${release_version}-release&lt;/code> branch, merging back to the trunk after the final release is complete.&lt;/p></description></item><item><title>Java SDK Release Process</title><link>https://deploy-preview-3199--dubbo.netlify.app/en/contact/committer/release-guide/java-sdk/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://deploy-preview-3199--dubbo.netlify.app/en/contact/committer/release-guide/java-sdk/</guid><description>&lt;h2 id="understanding-apache-release-content-and-process">Understanding Apache Release Content and Process&lt;/h2>
&lt;p>In general, the Source Release is the focus of Apache and is a necessary component of the release; the Binary Release is optional, and Dubbo can choose whether to publish binary packages to the Apache repository or to the Maven Central repository.&lt;/p>
&lt;p>Please refer to the following links for more information about ASF&amp;rsquo;s release guidelines:&lt;/p>
&lt;ul>
&lt;li>&lt;a href="http://www.apache.org/dev/release-publishing">Apache Release Guide&lt;/a>&lt;/li>
&lt;li>&lt;a href="http://www.apache.org/dev/release.html">Apache Release Policy&lt;/a>&lt;/li>
&lt;li>&lt;a href="http://www.apache.org/dev/publishing-maven-artifacts.html">Maven Release Info&lt;/a>&lt;/li>
&lt;/ul>
&lt;h2 id="local-build-environment-preparation">Local Build Environment Preparation&lt;/h2>
&lt;p>Mainly includes preparation for signing tools and Maven repository authentication.&lt;/p></description></item></channel></rss>