You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@iceberg.apache.org by gi...@apache.org on 2023/03/31 02:58:07 UTC

[iceberg-docs] branch asf-site updated: deploy: 61174bc1362478f463f26439ff2e5bb8f56d52e6

This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/iceberg-docs.git


The following commit(s) were added to refs/heads/asf-site by this push:
     new f9cb878d deploy: 61174bc1362478f463f26439ff2e5bb8f56d52e6
f9cb878d is described below

commit f9cb878d759dae7e073f5b7be0ec3a85145f0ce4
Author: jackye1995 <ja...@users.noreply.github.com>
AuthorDate: Fri Mar 31 02:58:03 2023 +0000

    deploy: 61174bc1362478f463f26439ff2e5bb8f56d52e6
---
 common/index.xml           |  6 +++---
 getting-started/index.html | 20 +-------------------
 how-to-release/index.html  | 27 +++++++++++++++++----------
 index.xml                  |  6 +++---
 4 files changed, 24 insertions(+), 35 deletions(-)

diff --git a/common/index.xml b/common/index.xml
index 1649ed4e..36b4c19a 100644
--- a/common/index.xml
+++ b/common/index.xml
@@ -12,9 +12,9 @@ Community discussions happen primarily on the dev mailing list, on apache-iceber
 Contribute See Contributing for more details on how to contribute to Iceberg.
 Issues Issues are tracked in GitHub:
 View open issues Open a new issue Slack We use the Apache Iceberg workspace on Slack. To be invited, follow this invite link.</description></item><item><title>Contribute</title><link>https://iceberg.apache.org/contribute/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/contribute/</guid><description>Contributing In this page, you will find some guidelines on contributing to Apache Iceberg. Please keep in mind that none of these are hard rules and  [...]
-If you are thinking of contributing but first would like to discuss the change you wish to make, we welcome you to head over to the Community page on the official Iceberg documentation site to find a number of ways to connect with the community, including slack and our mailing lists.</description></item><item><title>How To Release</title><link>https://iceberg.apache.org/how-to-release/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/how-to-release [...]
-Apache LDAP credentals for Nexus and SVN A GPG key for signing, published in KEYS If you have not published your GPG key yet, you must publish it before sending the vote email by doing:
-svn co https://dist.apache.org/repos/dist/dev/iceberg icebergsvn cd icebergsvn echo &amp;#34;&amp;#34; &amp;gt;&amp;gt; KEYS # append a newline gpg --list-sigs &amp;lt;YOUR KEY ID HERE&amp;gt; &amp;gt;&amp;gt; KEYS # append signatures gpg --armor --export &amp;lt;YOUR KEY ID HERE&amp;gt; &amp;gt;&amp;gt; KEYS # append public key block svn commit -m &amp;#34;add key for &amp;lt;YOUR NAME HERE&amp;gt;&amp;#34; Nexus access Nexus credentials are configured in your personal ~/.</description> [...]
+If you are thinking of contributing but first would like to discuss the change you wish to make, we welcome you to head over to the Community page on the official Iceberg documentation site to find a number of ways to connect with the community, including slack and our mailing lists.</description></item><item><title>How To Release</title><link>https://iceberg.apache.org/how-to-release/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/how-to-release [...]
+Decisions about releases are made by three groups:
+Release Manager: Does the work of creating the release, signing it, counting votes, announcing the release and so on. Requires the assistance of a committer for some steps. The community: Performs the discussion of whether it is the right time to create a release and what that release should contain.</description></item><item><title>Iceberg Catalogs</title><link>https://iceberg.apache.org/concepts/catalog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apac [...]
 Multi-Version Support Processing engine connectors maintained in the iceberg repository are built for multiple versions.</description></item><item><title>Puffin Spec</title><link>https://iceberg.apache.org/puffin-spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/puffin-spec/</guid><description>Puffin file format This is a specification for Puffin, a file format designed to store information such as indexes and statistics about data managed in  [...]
 Format specification A file conforming to the Puffin file format specification should have the structure as described below.</description></item><item><title>Roadmap</title><link>https://iceberg.apache.org/roadmap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/roadmap/</guid><description> Roadmap Overview This roadmap outlines projects that the Iceberg community is working on, their priority, and a rough size estimate. This is based on the lates [...]
 Priority 1 API: Iceberg 1.0.0 [medium] Python: Pythonic refactor [medium] Spec: Z-ordering / Space-filling curves [medium] Spec: Snapshot tagging and branching [small] Views: Spec [medium] Puffin: Implement statistics information in table snapshot [medium] Flink: FLIP-27 based Iceberg source [large] Priority 2 ORC: Support delete files stored as ORC [small] Spark: DSv2 streaming improvements [small] Flink: Inline file compaction [small] Flink: Support UPSERT [small] Spec: Secondary index [...]
diff --git a/getting-started/index.html b/getting-started/index.html
index b3c6e0d8..52cc0335 100644
--- a/getting-started/index.html
+++ b/getting-started/index.html
@@ -1,19 +1 @@
-<!--
- - Licensed to the Apache Software Foundation (ASF) under one or more
- - contributor license agreements.  See the NOTICE file distributed with
- - this work for additional information regarding copyright ownership.
- - The ASF licenses this file to You under the Apache License, Version 2.0
- - (the "License"); you may not use this file except in compliance with
- - the License.  You may obtain a copy of the License at
- -
- -   http://www.apache.org/licenses/LICENSE-2.0
- -
- - Unless required by applicable law or agreed to in writing, software
- - distributed under the License is distributed on an "AS IS" BASIS,
- - WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- - See the License for the specific language governing permissions and
- - limitations under the License.
- -->
-<head>
-  <meta http-equiv="Refresh" content="0; url='/docs/latest/getting-started'" />
-</head>
+<!doctype html><html lang=en-us><head><title>https://iceberg.apache.org/spark-quickstart/</title><link rel=canonical href=https://iceberg.apache.org/spark-quickstart/><meta name=robots content="noindex"><meta charset=utf-8><meta http-equiv=refresh content="0; url=https://iceberg.apache.org/spark-quickstart/"></head></html>
\ No newline at end of file
diff --git a/how-to-release/index.html b/how-to-release/index.html
index e161b91a..4fa7517a 100644
--- a/how-to-release/index.html
+++ b/how-to-release/index.html
@@ -3,7 +3,7 @@
 <span class=icon-bar></span>
 <span class=icon-bar></span>
 <span class=icon-bar></span></button>
-<a class="page-scroll navbar-brand" href=https://iceberg.apache.org/><img class=top-navbar-logo src=https://iceberg.apache.org//img/iceberg-logo-icon.png> Apache Iceberg</a></div><div><input type=search class=form-control id=search-input placeholder=Search... maxlength=64 data-hotkeys=s/></div><div class=versions-dropdown><span>1.2.0</span> <i class="fa fa-chevron-down"></i><div class=versions-dropdown-content><ul><li class=versions-dropdown-selection><a href=/docs/latest>latest</a></li> [...]
+<a class="page-scroll navbar-brand" href=https://iceberg.apache.org/><img class=top-navbar-logo src=https://iceberg.apache.org//img/iceberg-logo-icon.png> Apache Iceberg</a></div><div><input type=search class=form-control id=search-input placeholder=Search... maxlength=64 data-hotkeys=s/></div><div class=versions-dropdown><span>1.2.0</span> <i class="fa fa-chevron-down"></i><div class=versions-dropdown-content><ul><li class=versions-dropdown-selection><a href=/docs/latest>latest</a></li> [...]
 </span></span><span style=display:flex><span>cd icebergsvn
 </span></span><span style=display:flex><span>echo <span style=color:#e6db74>&#34;&#34;</span> &gt;&gt; KEYS <span style=color:#75715e># append a newline</span>
 </span></span><span style=display:flex><span>gpg --list-sigs &lt;YOUR KEY ID HERE&gt; &gt;&gt; KEYS <span style=color:#75715e># append signatures</span>
@@ -13,7 +13,7 @@
 mavenPassword=SomePassword
 </code></pre><h3 id=pgp-signing>PGP signing</h3><p>The release scripts use the command-line <code>gpg</code> utility so that signing can use the gpg-agent and does not require writing your private key&rsquo;s passphrase to a configuration file.</p><p>To configure gradle to sign convenience binary artifacts, add the following settings to <code>~/.gradle/gradle.properties</code>:</p><pre tabindex=0><code>signing.gnupg.keyName=Your Name (CODE SIGNING KEY)
 </code></pre><p>To use <code>gpg</code> instead of <code>gpg2</code>, also set <code>signing.gnupg.executable=gpg</code></p><p>For more information, see the Gradle <a href=https://docs.gradle.org/current/userguide/signing_plugin.html#sec:signatory_credentials>signing documentation</a>.</p><h3 id=apache-repository>Apache repository</h3><p>The release should be executed against <code>https://github.com/apache/iceberg.git</code> instead of any fork.
-Set it as remote with name <code>apache</code> for release if it is not already set up.</p><h2 id=creating-a-release-candidate>Creating a release candidate</h2><h3 id=build-the-source-release>Build the source release</h3><p>To create the source release artifacts, run the <code>source-release.sh</code> script with the release version and release candidate number:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4>< [...]
+Set it as remote with name <code>apache</code> for release if it is not already set up.</p><h2 id=creating-a-release-candidate>Creating a release candidate</h2><h3 id=initiate-a-discussion-about-the-release-with-the-community>Initiate a discussion about the release with the community</h3><p>This step can be useful to gather ongoing patches that the community thinks should be in the upcoming release.</p><p>The communication can be started via a [DISCUSS] mail on the dev@ channel and the d [...]
 </span></span></code></pre></div><p>Example console output:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-text data-lang=text><span style=display:flex><span>Preparing source for apache-iceberg-0.13.0-rc1
 </span></span><span style=display:flex><span>Adding version.txt and tagging release...
 </span></span><span style=display:flex><span>[master ca8bb7d0] Add version.txt for release 0.13.0
@@ -83,11 +83,15 @@ The email template is already generated in <code>release-announcement-email.txt<
 </span></span><span style=display:flex><span>
 </span></span><span style=display:flex><span>Please download, verify, and test.
 </span></span><span style=display:flex><span>
-</span></span><span style=display:flex><span>Please vote in the next 72 hours.
+</span></span><span style=display:flex><span>Please vote in the next 72 hours. (Weekends excluded)
 </span></span><span style=display:flex><span>
 </span></span><span style=display:flex><span>[ ] +1 Release this as Apache Iceberg &lt;VERSION&gt;
 </span></span><span style=display:flex><span>[ ] +0
 </span></span><span style=display:flex><span>[ ] -1 Do not release this because...
+</span></span><span style=display:flex><span>
+</span></span><span style=display:flex><span>Only PMC members have binding votes, but other community members are encouraged to cast
+</span></span><span style=display:flex><span>non-binding votes. This vote will pass if there are 3 binding +1 votes and more binding
+</span></span><span style=display:flex><span>+1 votes than -1 votes.
 </span></span></code></pre></div><p>When a candidate is passed or rejected, reply with the voting result:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-text data-lang=text><span style=display:flex><span>Subject: [RESULT][VOTE] Release Apache Iceberg &lt;VERSION&gt; RC&lt;NUM&gt;
 </span></span></code></pre></div><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-text data-lang=text><span style=display:flex><span>Thanks everyone who participated in the vote for Release Apache Iceberg &lt;VERSION&gt; RC&lt;NUM&gt;.
 </span></span><span style=display:flex><span>
@@ -98,7 +102,9 @@ The email template is already generated in <code>release-announcement-email.txt<
 </span></span><span style=display:flex><span>-1: 0 (binding), 0 (non-binding)
 </span></span><span style=display:flex><span>
 </span></span><span style=display:flex><span>Therefore, the release candidate is passed/rejected.
-</span></span></code></pre></div><h3 id=finishing-the-release>Finishing the release</h3><p>After the release vote has passed, you need to release the last candidate&rsquo;s artifacts.</p><p>First, copy the source release directory to releases:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-bash data-lang=bash><span style=display:flex><span>mkdir iceberg
+</span></span></code></pre></div><h3 id=finishing-the-release>Finishing the release</h3><p>After the release vote has passed, you need to release the last candidate&rsquo;s artifacts.</p><p>But note that releasing the artifacts should happen around the same time the new docs are released
+so make sure the <a href=/how-to-release/#documentation-release>documentation changes</a>
+are prepared when going through the below steps.</p><h4 id=publishing-the-release>Publishing the release</h4><p>First, copy the source release directory to releases:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-bash data-lang=bash><span style=display:flex><span>mkdir iceberg
 </span></span><span style=display:flex><span>cd iceberg
 </span></span><span style=display:flex><span>svn co https://dist.apache.org/repos/dist/dev/iceberg candidates
 </span></span><span style=display:flex><span>svn co https://dist.apache.org/repos/dist/release/iceberg releases
@@ -106,8 +112,9 @@ The email template is already generated in <code>release-announcement-email.txt<
 </span></span><span style=display:flex><span>cd releases
 </span></span><span style=display:flex><span>svn add apache-iceberg-&lt;VERSION&gt;
 </span></span><span style=display:flex><span>svn ci -m <span style=color:#e6db74>&#39;Iceberg: Add release &lt;VERSION&gt;&#39;</span>
-</span></span></code></pre></div><p>Next, add a release tag to the git repository based on the passing candidate tag:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-bash data-lang=bash><span style=display:flex><span>git tag -am <span style=color:#e6db74>&#39;Release Apache Iceberg &lt;VERSION&gt;&#39;</span> apache-iceberg-&lt;VERSION&gt; apache-iceberg-&lt;VERSION&gt;-rcN
-</span></span></code></pre></div><p>Then release the candidate repository in <a href=https://repository.apache.org/#stagingRepositories>Nexus</a>.</p><p>To announce the release, wait until Maven central has mirrored the Apache binaries, then update the Iceberg site and send an announcement email:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-text data-lang=text><span style=display:flex><s [...]
+</span></span></code></pre></div><p>!!! Note
+The above step requires PMC privileges to execute.</p><p>Next, add a release tag to the git repository based on the passing candidate tag:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-bash data-lang=bash><span style=display:flex><span>git tag -am <span style=color:#e6db74>&#39;Release Apache Iceberg &lt;VERSION&gt;&#39;</span> apache-iceberg-&lt;VERSION&gt; apache-iceberg-&lt;VERSION&gt;-rcN
+</span></span></code></pre></div><p>Then release the candidate repository in <a href=https://repository.apache.org/#stagingRepositories>Nexus</a>.</p><h4 id=announcing-the-release>Announcing the release</h4><p>To announce the release, wait until Maven central has mirrored the Apache binaries, then update the Iceberg site and send an announcement email:</p><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class [...]
 </span></span></code></pre></div><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-text data-lang=text><span style=display:flex><span>I&#39;m pleased to announce the release of Apache Iceberg &lt;VERSION&gt;!
 </span></span><span style=display:flex><span>
 </span></span><span style=display:flex><span>Apache Iceberg is an open table format for huge analytic datasets. Iceberg
@@ -120,11 +127,11 @@ The email template is already generated in <code>release-announcement-email.txt<
 </span></span><span style=display:flex><span>Java artifacts are available from Maven Central.
 </span></span><span style=display:flex><span>
 </span></span><span style=display:flex><span>Thanks to everyone for contributing!
-</span></span></code></pre></div><h3 id=documentation-release>Documentation Release</h3><p>Documentation needs to be updated as a part of an Iceberg release after a release candidate is passed.
+</span></span></code></pre></div><h4 id=update-revapi>Update revapi</h4><p>Create a PR in the <code>iceberg</code> repo to make revapi run on the new release. For an example see <a href=https://github.com/apache/iceberg/pull/6275>this PR</a>.</p><h4 id=update-github-issue-template>Update github issue template</h4><p>Create a PR in the <code>iceberg</code> repo to add the new version to the github issue template. For an example see <a href=https://github.com/apache/iceberg/pull/6287>this  [...]
 The commands described below assume you are in a directory containing a local clone of the <code>iceberg-docs</code>
 repository and <code>iceberg</code> repository. Adjust the commands accordingly if it is not the case. Note that all
 changes in <code>iceberg</code> need to happen against the <code>master</code> branch and changes in <code>iceberg-docs</code> need to happen
-against the <code>main</code> branch.</p><h4 id=iceberg-repository-preparations>iceberg repository preparations</h4><p>A PR needs to be published in the <code>iceberg</code> repository with the following changes:</p><ol><li>Create a new folder called <code>docs/releases/&lt;VERSION NUMBER></code> with an <code>_index.md</code> file. See the existing folders under <code>docs/releases</code> for more details.</li></ol><h4 id=common-documentation-update>Common documentation update</h4><ol>< [...]
+against the <code>main</code> branch.</p><h4 id=common-documentation-update>Common documentation update</h4><ol><li>To start the release process, run the following steps in the <code>iceberg-docs</code> repository to copy docs over:</li></ol><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-shell data-lang=shell><span style=display:flex><span>cp -r ../iceberg/format/* ../iceberg-docs/landing-pag [...]
 </span></span></code></pre></div><ol start=2><li>Change into the <code>iceberg-docs</code> repository and create a branch.</li></ol><div class=highlight><pre tabindex=0 style=color:#f8f8f2;background-color:#272822;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code class=language-shell data-lang=shell><span style=display:flex><span>cd ../iceberg-docs
 </span></span><span style=display:flex><span>git checkout -b &lt;BRANCH NAME&gt;
 </span></span></code></pre></div><ol start=3><li>Commit, push, and open a PR against the <code>iceberg-docs</code> repo (<code>&lt;BRANCH NAME></code> -> <code>main</code>)</li></ol><h4 id=versioned-documentation-update>Versioned documentation update</h4><p>Once the common docs changes have been merged into <code>main</code>, the next step is to update the versioned docs.</p><ol><li>In the <code>iceberg-docs</code> repository, cut a new branch using the version number as the branch name< [...]
@@ -141,7 +148,7 @@ against the <code>main</code> branch.</p><h4 id=iceberg-repository-preparations>
 </span></span><span style=display:flex><span>git push apache latest
 </span></span></code></pre></div><h4 id=set-latest-version-in-iceberg-docs-repo>Set latest version in iceberg-docs repo</h4><p>The last step is to update the <code>main</code> branch in <code>iceberg-docs</code> to set the latest version.
 A PR needs to be published in the <code>iceberg-docs</code> repository with the following changes:</p><ol><li>Update variable <code>latestVersions.iceberg</code> to the new release version in <code>landing-page/config.toml</code></li><li>Update variable <code>latestVersions.iceberg</code> to the new release version and
-<code>versions.nessie</code> to the version of <code>org.projectnessie.nessie:*</code> from <a href=https://github.com/apache/iceberg/blob/master/versions.props>versions.props</a> in <code>docs/config.toml</code></li><li>Mark the current latest release notes to past releases under <code>landing-page/content/common/release-notes.md</code></li><li>Add release notes for the new release version in <code>landing-page/content/common/release-notes.md</code></li></ol><h1 id=how-to-verify-a-relea [...]
+<code>versions.nessie</code> to the version of <code>org.projectnessie.nessie:*</code> from <a href=https://github.com/apache/iceberg/blob/master/versions.props>versions.props</a> in <code>docs/config.toml</code></li><li>Update list <code>versions</code> with the new release in <code>landing-page/config.toml</code></li><li>Update list <code>versions</code> with the new release in <code>docs/config.toml</code></li><li>Mark the current latest release notes to past releases under <code>land [...]
 will prepare a release candidate and call a vote on the Iceberg
 <a href=https://iceberg.apache.org/#community/#mailing-lists>dev list</a>.
 To validate the release candidate, community members will test it out in their downstream projects and environments.
@@ -194,7 +201,7 @@ with either <code>+1</code>, <code>0</code>, or <code>-1</code>.</p><blockquote>
 [ ] -1 Do not release this because&mldr;</p></blockquote><p>In addition to your vote, it&rsquo;s customary to specify if your vote is binding or non-binding. Only members
 of the Project Management Committee have formally binding votes. If you&rsquo;re unsure, you can specify that your
 vote is non-binding. To read more about voting in the Apache framework, checkout the
-<a href=https://www.apache.org/foundation/voting.html>Voting</a> information page on the Apache foundation&rsquo;s website.</p></div><div id=toc class=markdown-body><div id=full><nav id=TableOfContents><ul><li><a href=#setup>Setup</a><ul><li><a href=#nexus-access>Nexus access</a></li><li><a href=#pgp-signing>PGP signing</a></li><li><a href=#apache-repository>Apache repository</a></li></ul></li><li><a href=#creating-a-release-candidate>Creating a release candidate</a><ul><li><a href=#buil [...]
+<a href=https://www.apache.org/foundation/voting.html>Voting</a> information page on the Apache foundation&rsquo;s website.</p></div><div id=toc class=markdown-body><div id=full><nav id=TableOfContents><ul><li><a href=#introduction>Introduction</a></li><li><a href=#setup>Setup</a><ul><li><a href=#nexus-access>Nexus access</a></li><li><a href=#pgp-signing>PGP signing</a></li><li><a href=#apache-repository>Apache repository</a></li></ul></li><li><a href=#creating-a-release-candidate>Creati [...]
 <script src=https://iceberg.apache.org//js/jquery.easing.min.js></script>
 <script type=text/javascript src=https://iceberg.apache.org//js/search.js></script>
 <script src=https://iceberg.apache.org//js/bootstrap.min.js></script>
diff --git a/index.xml b/index.xml
index fd8e6f73..e2a64f0d 100644
--- a/index.xml
+++ b/index.xml
@@ -12,9 +12,9 @@ Community discussions happen primarily on the dev mailing list, on apache-iceber
 Contribute See Contributing for more details on how to contribute to Iceberg.
 Issues Issues are tracked in GitHub:
 View open issues Open a new issue Slack We use the Apache Iceberg workspace on Slack. To be invited, follow this invite link.</description></item><item><title>Contribute</title><link>https://iceberg.apache.org/contribute/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/contribute/</guid><description>Contributing In this page, you will find some guidelines on contributing to Apache Iceberg. Please keep in mind that none of these are hard rules and  [...]
-If you are thinking of contributing but first would like to discuss the change you wish to make, we welcome you to head over to the Community page on the official Iceberg documentation site to find a number of ways to connect with the community, including slack and our mailing lists.</description></item><item><title>How To Release</title><link>https://iceberg.apache.org/how-to-release/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/how-to-release [...]
-Apache LDAP credentals for Nexus and SVN A GPG key for signing, published in KEYS If you have not published your GPG key yet, you must publish it before sending the vote email by doing:
-svn co https://dist.apache.org/repos/dist/dev/iceberg icebergsvn cd icebergsvn echo &amp;#34;&amp;#34; &amp;gt;&amp;gt; KEYS # append a newline gpg --list-sigs &amp;lt;YOUR KEY ID HERE&amp;gt; &amp;gt;&amp;gt; KEYS # append signatures gpg --armor --export &amp;lt;YOUR KEY ID HERE&amp;gt; &amp;gt;&amp;gt; KEYS # append public key block svn commit -m &amp;#34;add key for &amp;lt;YOUR NAME HERE&amp;gt;&amp;#34; Nexus access Nexus credentials are configured in your personal ~/.</description> [...]
+If you are thinking of contributing but first would like to discuss the change you wish to make, we welcome you to head over to the Community page on the official Iceberg documentation site to find a number of ways to connect with the community, including slack and our mailing lists.</description></item><item><title>How To Release</title><link>https://iceberg.apache.org/how-to-release/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/how-to-release [...]
+Decisions about releases are made by three groups:
+Release Manager: Does the work of creating the release, signing it, counting votes, announcing the release and so on. Requires the assistance of a committer for some steps. The community: Performs the discussion of whether it is the right time to create a release and what that release should contain.</description></item><item><title>Iceberg Catalogs</title><link>https://iceberg.apache.org/concepts/catalog/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apac [...]
 Multi-Version Support Processing engine connectors maintained in the iceberg repository are built for multiple versions.</description></item><item><title>Puffin Spec</title><link>https://iceberg.apache.org/puffin-spec/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/puffin-spec/</guid><description>Puffin file format This is a specification for Puffin, a file format designed to store information such as indexes and statistics about data managed in  [...]
 Format specification A file conforming to the Puffin file format specification should have the structure as described below.</description></item><item><title>Roadmap</title><link>https://iceberg.apache.org/roadmap/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://iceberg.apache.org/roadmap/</guid><description> Roadmap Overview This roadmap outlines projects that the Iceberg community is working on, their priority, and a rough size estimate. This is based on the lates [...]
 Priority 1 API: Iceberg 1.0.0 [medium] Python: Pythonic refactor [medium] Spec: Z-ordering / Space-filling curves [medium] Spec: Snapshot tagging and branching [small] Views: Spec [medium] Puffin: Implement statistics information in table snapshot [medium] Flink: FLIP-27 based Iceberg source [large] Priority 2 ORC: Support delete files stored as ORC [small] Spark: DSv2 streaming improvements [small] Flink: Inline file compaction [small] Flink: Support UPSERT [small] Spec: Secondary index [...]