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/parquet-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new df4c623 deploy: de8fc26563951c0d47bc8f157bacf9c64fe3e012
df4c623 is described below
commit df4c623a7a5b6bce98ae607c03b750385b90ddc3
Author: wgtmac <[email protected]>
AuthorDate: Tue Aug 6 09:30:33 2024 +0000
deploy: de8fc26563951c0d47bc8f157bacf9c64fe3e012
---
output/docs/_print/index.html | 32 ++++-----
.../docs/contribution-guidelines/_print/index.html | 32 ++++-----
output/docs/contribution-guidelines/index.html | 2 +-
output/docs/contribution-guidelines/index.xml | 79 +++++++++-------------
.../contribution-guidelines/releasing/index.html | 42 ++++++------
output/docs/index.xml | 79 +++++++++-------------
output/sitemap.xml | 2 +-
7 files changed, 111 insertions(+), 157 deletions(-)
diff --git a/output/docs/_print/index.html b/output/docs/_print/index.html
index 7c77db7..b71f857 100644
--- a/output/docs/_print/index.html
+++ b/output/docs/_print/index.html
@@ -823,13 +823,13 @@ Java resources can be build using <code>mvn
package</code>. The current stable v
</span></span><span style=display:flex><span>git push
github-apache/parquet-1.14.x
</span></span></code></pre></div><h2 id=website>Website</h2><h3
id=release-documentation>Release Documentation</h3><p>To create documentation
for a new release of <code>parquet-format</code> create a new
<releasenumber>.md file under <code>content/en/blog/parquet-format</code>.
Please see existing files in that directory as an example.</p><p>To create
documentation for a new release of <code>parquet-java</code> create a new
<releasenumber>.md file under <code>content/en/blog/parquet-java [...]
job in the <a
href=https://github.com/apache/parquet-site/blob/staging/.github/workflows/deploy.yml>deployment
workflow</a> will be run, populating the <code>asf-staging</code> branch on
this repo with the necessary files.</li></ol><p><strong>Do not directly edit
the <code>asf-staging</code> branch of this repo</strong></p><h4
id=production>Production</h4><p>To make a change to the <code>production</code>
version of the website:</p><ol><li>Make a PR against the
<code>production</code> br [...]
-job in the <a
href=https://github.com/apache/parquet-site/blob/production/.github/workflows/deploy.yml>deployment
workflow</a> will be run, populating the <code>asf-site</code> branch on this
repo with the necessary files.</li></ol><p><strong>Do not directly edit the
<code>asf-site</code> branch of this repo</strong></p></div><div
class=td-content style=page-break-before:always><h1
id=pg-d65ca0c6c1ffbeb20627c4d33e7e3dc4>4.4 - Releasing Parquet</h1><div
class=lead>How to release Parquet</ [...]
-</code></pre><p>If you have problems, read the <a
href=https://www.apache.org/dev/publishing-maven-artifacts.html>publishing
Maven artifacts documentation</a></p><h3 id=release-process>Release
process</h3><p>Parquet uses the maven-release-plugin to tag a release and push
binary artifacts to staging in Nexus. Once maven completes the release, the
official source tarball is built from the tag.</p><p>Before you start the
release process:</p><ol><li>Verify that the release is finished (no pl [...]
-</code></pre><p>This runs maven’s release prepare with a consistent tag name.
After this step, the release tag will exist in the git repository.</p><p>If
this step fails, you can roll back the changes by running these
commands.</p><pre><code>find ./ -type f -name '*.releaseBackup' -exec rm {} \;
-find ./ -type f -name 'pom.xml' -exec git checkout {} \;
-</code></pre><h4 id=2-run-releaseperform-to-stage-binaries>2. Run
release:perform to stage binaries</h4><pre><code>mvn release:perform
-</code></pre><p>This uploads binary artifacts for the release tag to <a
href=https://repository.apache.org/>Nexus</a>.</p><h4
id=3-in-nexus-close-the-staging-repository>3. In Nexus, close the staging
repository</h4><p>Closing a staging repository makes the binaries available in
<a
href=https://repository.apache.org/content/groups/staging/org/apache/parquet/>staging</a>,
but does not publish them.</p><ol><li>Go to <a
href=https://repository.apache.org/>Nexus</a>.</li><li>In the menu on th [...]
-</code></pre><p>This script builds the source tarball from the release tag’s
SHA1, signs it, and uploads the necessary files with SVN.</p><p>The source
release is pushed to <a
href=https://dist.apache.org/repos/dist/dev/parquet/>https://dist.apache.org/repos/dist/dev/parquet/</a></p><p>The
last message from the script is the release commit’s SHA1 hash and URL for the
VOTE e-mail.</p><h4
id=5-send-a-vote-e-mail-to-devparquetapacheorgmailtodevparquetapacheorg>5. Send
a VOTE e-mail to <a hr [...]
+job in the <a
href=https://github.com/apache/parquet-site/blob/production/.github/workflows/deploy.yml>deployment
workflow</a> will be run, populating the <code>asf-site</code> branch on this
repo with the necessary files.</li></ol><p><strong>Do not directly edit the
<code>asf-site</code> branch of this repo</strong></p></div><div
class=td-content style=page-break-before:always><h1
id=pg-d65ca0c6c1ffbeb20627c4d33e7e3dc4>4.4 - Releasing Parquet</h1><div
class=lead>How to release Parquet-J [...]
+</span></span></code></pre></div><p>If you have problems, read the <a
href=https://www.apache.org/dev/publishing-maven-artifacts.html>publishing
Maven artifacts documentation</a>.</p><h3 id=release-process>Release
process</h3><p>Parquet uses the maven-release-plugin to tag a release and push
binary artifacts to staging in Nexus. Once maven completes the release, the
official source tarball is built from the tag.</p><p>Before you start the
release process:</p><ol><li>Verify that the relea [...]
+</span></span></code></pre></div><p>This runs maven’s release prepare with a
consistent tag name. After this step, the release tag will exist in the git
repository.</p><p>If this step fails, you can roll back the changes by running
these commands.</p><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>find ./ -type f
-name <span style=color:#4e9a06>'*.releaseBa [...]
+</span></span><span style=display:flex><span>find ./ -type f -name <span
style=color:#4e9a06>'pom.xml'</span> -exec git checkout <span
style=color:#ce5c00;font-weight:700>{}</span> <span
style=color:#4e9a06>\;</span>
+</span></span></code></pre></div><h4
id=2-run-releaseperform-to-stage-binaries>2. Run release:perform to stage
binaries</h4><p>Upload binary artifacts for the release tag to <a
href=https://repository.apache.org/>Nexus</a>:</p><div class=highlight><pre
tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>mvn
release:perform
+</span></span></code></pre></div><h4
id=3-in-nexus-close-the-staging-repository>3. In Nexus, close the staging
repository</h4><p>Closing a staging repository makes the binaries available in
<a
href=https://repository.apache.org/content/groups/staging/org/apache/parquet/>staging</a>,
but does not publish them.</p><ol><li>Go to <a
href=https://repository.apache.org/>Nexus</a>.</li><li>In the menu on the left,
choose “Staging Repositories”.</li><li>Select the Parquet
repository.</li><li>At [...]
+</span></span></code></pre></div><p>This script builds the source tarball from
the release tag’s SHA1, signs it, and uploads the necessary files with
SVN.</p><p>The source release is pushed to <a
href=https://dist.apache.org/repos/dist/dev/parquet/>https://dist.apache.org/repos/dist/dev/parquet/</a></p><p>The
last message from the script is the release commit’s SHA1 hash and URL for the
VOTE e-mail.</p><h3 id=5-prepare-the-pre-release>5. Prepare the
pre-release</h3><p>Creating the <a hre [...]
Hi everyone,
@@ -846,6 +846,9 @@ The release tarball, signature, and checksums are here:
You can find the KEYS file here:
* https://downloads.apache.org/parquet/KEYS
+You can find the changelog here:
+https://github.com/apache/parquet-java/releases/tag/apache-parquet-<VERSION>-rc<NUM>
+
Binary artifacts are staged in Nexus here:
* https://repository.apache.org/content/groups/staging/org/apache/parquet/
@@ -858,16 +861,9 @@ Please vote in the next 72 hours.
[ ] +1 Release this as Apache Parquet <VERSION>
[ ] +0
[ ] -1 Do not release this because...
-</code></pre><h3 id=publishing-after-the-vote-passes>Publishing after the vote
passes</h3><p>After a release candidate passes a vote, the candidate needs to
be published as the final release.</p><h4
id=1-tag-final-release-and-set-development-version>1. Tag final release and set
development version</h4><pre><code>dev/finalize-release <release-version>
<rc-num> <new-development-version-without-SNAPSHOT-suffix>
-</code></pre><p>This will add the final release tag to the RC tag and sets the
new development version in the pom files. If everything is fine push the
changes and the new tag to github: <code>git push --follow-tags</code></p><h4
id=2-release-the-binary-repository-in-nexus>2. Release the binary repository in
Nexus</h4><p>Releasing a binary repository publishes the binaries to <a
href=https://repository.apache.org/content/groups/public/org/apache/parquet/>public</a>.</p><ol><li>Go
to <a h [...]
-cd parquet
-svn co https://dist.apache.org/repos/dist/dev/parquet candidates
-svn co https://dist.apache.org/repos/dist/release/parquet releases
-</code></pre><p>Next, copy the directory for the release candidate the passed
from candidates to releases and rename it; remove the “-rcN” part of the
directory name.</p><pre><code>cp -r
candidates/apache-parquet-<VERSION>-rcN/
releases/apache-parquet-<VERSION>
-</code></pre><p>Then add and commit the release artifacts:</p><pre><code>cd
releases
-svn add apache-parquet-<version>
-svn ci -m "Parquet: Add release <VERSION>"
-</code></pre><h4 id=4-update-parquetapacheorg>4. Update
parquet.apache.org</h4><p>Update the downloads page on parquet.apache.org.
Instructions for updating the site are on the <a
href=https://parquet.apache.org/docs/contribution-guidelines/contributing/>contribution
page</a>.</p><h4
id=5-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list>5.
Send an ANNOUNCE e-mail to <a
href=mailto:[email protected]>[email protected]</a> and the dev
list</h4><pre><c [...]
+</code></pre><h3 id=publishing-after-the-vote-passes>Publishing after the vote
passes</h3><p>After a release candidate passes a vote, the candidate needs to
be published as the final release.</p><h4
id=1-tag-final-release-and-set-development-version>1. Tag final release and set
development version</h4><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>./dev/finali [...]
+</span></span></code></pre></div><p>This will add the final release tag to the
RC tag and sets the new development version in the pom files. If everything is
fine push the changes and the new tag to GitHub: <code>git push
--follow-tags</code></p><h4 id=2-release-the-binary-repository-in-nexus>2.
Release the binary repository in Nexus</h4><p>Releasing a binary repository
publishes the binaries to <a
href=https://repository.apache.org/content/groups/public/org/apache/parquet/>public</a>.</
[...]
+</span></span></code></pre></div><h4 id=4-update-parquetapacheorg>4. Update
parquet.apache.org</h4><p>Update the downloads page on parquet.apache.org.
Instructions for updating the site are on the <a
href=https://parquet.apache.org/docs/contribution-guidelines/contributing/>contribution
page</a>.</p><h3 id=5-add-the-release-to-github>5. Add the release to
GitHub</h3><p>Add a <a
href=https://github.com/apache/parquet-java/releases/new>new release to
GitHub</a>. First select the newly tag [...]
I'm please to announce the release of Parquet <VERSION>!
@@ -876,7 +872,7 @@ Parquet is a general-purpose columnar file format for
nested data. It uses
space-efficient encodings and a compressed and splittable structure for
processing frameworks like Hadoop.
-Changes are listed at:
https://github.com/apache/parquet-mr/blob/apache-parquet-<VERSION>/CHANGES.md
+Changes are listed at:
https://github.com/apache/parquet-java/releases/tag/apache-parquet-<VERSION>
This release can be downloaded from: https://parquet.apache.org/downloads/
diff --git a/output/docs/contribution-guidelines/_print/index.html
b/output/docs/contribution-guidelines/_print/index.html
index d4d468f..84886df 100644
--- a/output/docs/contribution-guidelines/_print/index.html
+++ b/output/docs/contribution-guidelines/_print/index.html
@@ -13,13 +13,13 @@ Java resources can be build using <code>mvn package</code>.
The current stable v
</span></span><span style=display:flex><span>git push
github-apache/parquet-1.14.x
</span></span></code></pre></div><h2 id=website>Website</h2><h3
id=release-documentation>Release Documentation</h3><p>To create documentation
for a new release of <code>parquet-format</code> create a new
<releasenumber>.md file under <code>content/en/blog/parquet-format</code>.
Please see existing files in that directory as an example.</p><p>To create
documentation for a new release of <code>parquet-java</code> create a new
<releasenumber>.md file under <code>content/en/blog/parquet-java [...]
job in the <a
href=https://github.com/apache/parquet-site/blob/staging/.github/workflows/deploy.yml>deployment
workflow</a> will be run, populating the <code>asf-staging</code> branch on
this repo with the necessary files.</li></ol><p><strong>Do not directly edit
the <code>asf-staging</code> branch of this repo</strong></p><h4
id=production>Production</h4><p>To make a change to the <code>production</code>
version of the website:</p><ol><li>Make a PR against the
<code>production</code> br [...]
-job in the <a
href=https://github.com/apache/parquet-site/blob/production/.github/workflows/deploy.yml>deployment
workflow</a> will be run, populating the <code>asf-site</code> branch on this
repo with the necessary files.</li></ol><p><strong>Do not directly edit the
<code>asf-site</code> branch of this repo</strong></p></div><div
class=td-content style=page-break-before:always><h1
id=pg-d65ca0c6c1ffbeb20627c4d33e7e3dc4>4 - Releasing Parquet</h1><div
class=lead>How to release Parquet</di [...]
-</code></pre><p>If you have problems, read the <a
href=https://www.apache.org/dev/publishing-maven-artifacts.html>publishing
Maven artifacts documentation</a></p><h3 id=release-process>Release
process</h3><p>Parquet uses the maven-release-plugin to tag a release and push
binary artifacts to staging in Nexus. Once maven completes the release, the
official source tarball is built from the tag.</p><p>Before you start the
release process:</p><ol><li>Verify that the release is finished (no pl [...]
-</code></pre><p>This runs maven’s release prepare with a consistent tag name.
After this step, the release tag will exist in the git repository.</p><p>If
this step fails, you can roll back the changes by running these
commands.</p><pre><code>find ./ -type f -name '*.releaseBackup' -exec rm {} \;
-find ./ -type f -name 'pom.xml' -exec git checkout {} \;
-</code></pre><h4 id=2-run-releaseperform-to-stage-binaries>2. Run
release:perform to stage binaries</h4><pre><code>mvn release:perform
-</code></pre><p>This uploads binary artifacts for the release tag to <a
href=https://repository.apache.org/>Nexus</a>.</p><h4
id=3-in-nexus-close-the-staging-repository>3. In Nexus, close the staging
repository</h4><p>Closing a staging repository makes the binaries available in
<a
href=https://repository.apache.org/content/groups/staging/org/apache/parquet/>staging</a>,
but does not publish them.</p><ol><li>Go to <a
href=https://repository.apache.org/>Nexus</a>.</li><li>In the menu on th [...]
-</code></pre><p>This script builds the source tarball from the release tag’s
SHA1, signs it, and uploads the necessary files with SVN.</p><p>The source
release is pushed to <a
href=https://dist.apache.org/repos/dist/dev/parquet/>https://dist.apache.org/repos/dist/dev/parquet/</a></p><p>The
last message from the script is the release commit’s SHA1 hash and URL for the
VOTE e-mail.</p><h4
id=5-send-a-vote-e-mail-to-devparquetapacheorgmailtodevparquetapacheorg>5. Send
a VOTE e-mail to <a hr [...]
+job in the <a
href=https://github.com/apache/parquet-site/blob/production/.github/workflows/deploy.yml>deployment
workflow</a> will be run, populating the <code>asf-site</code> branch on this
repo with the necessary files.</li></ol><p><strong>Do not directly edit the
<code>asf-site</code> branch of this repo</strong></p></div><div
class=td-content style=page-break-before:always><h1
id=pg-d65ca0c6c1ffbeb20627c4d33e7e3dc4>4 - Releasing Parquet</h1><div
class=lead>How to release Parquet-Jav [...]
+</span></span></code></pre></div><p>If you have problems, read the <a
href=https://www.apache.org/dev/publishing-maven-artifacts.html>publishing
Maven artifacts documentation</a>.</p><h3 id=release-process>Release
process</h3><p>Parquet uses the maven-release-plugin to tag a release and push
binary artifacts to staging in Nexus. Once maven completes the release, the
official source tarball is built from the tag.</p><p>Before you start the
release process:</p><ol><li>Verify that the relea [...]
+</span></span></code></pre></div><p>This runs maven’s release prepare with a
consistent tag name. After this step, the release tag will exist in the git
repository.</p><p>If this step fails, you can roll back the changes by running
these commands.</p><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>find ./ -type f
-name <span style=color:#4e9a06>'*.releaseBa [...]
+</span></span><span style=display:flex><span>find ./ -type f -name <span
style=color:#4e9a06>'pom.xml'</span> -exec git checkout <span
style=color:#ce5c00;font-weight:700>{}</span> <span
style=color:#4e9a06>\;</span>
+</span></span></code></pre></div><h4
id=2-run-releaseperform-to-stage-binaries>2. Run release:perform to stage
binaries</h4><p>Upload binary artifacts for the release tag to <a
href=https://repository.apache.org/>Nexus</a>:</p><div class=highlight><pre
tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>mvn
release:perform
+</span></span></code></pre></div><h4
id=3-in-nexus-close-the-staging-repository>3. In Nexus, close the staging
repository</h4><p>Closing a staging repository makes the binaries available in
<a
href=https://repository.apache.org/content/groups/staging/org/apache/parquet/>staging</a>,
but does not publish them.</p><ol><li>Go to <a
href=https://repository.apache.org/>Nexus</a>.</li><li>In the menu on the left,
choose “Staging Repositories”.</li><li>Select the Parquet
repository.</li><li>At [...]
+</span></span></code></pre></div><p>This script builds the source tarball from
the release tag’s SHA1, signs it, and uploads the necessary files with
SVN.</p><p>The source release is pushed to <a
href=https://dist.apache.org/repos/dist/dev/parquet/>https://dist.apache.org/repos/dist/dev/parquet/</a></p><p>The
last message from the script is the release commit’s SHA1 hash and URL for the
VOTE e-mail.</p><h3 id=5-prepare-the-pre-release>5. Prepare the
pre-release</h3><p>Creating the <a hre [...]
Hi everyone,
@@ -36,6 +36,9 @@ The release tarball, signature, and checksums are here:
You can find the KEYS file here:
* https://downloads.apache.org/parquet/KEYS
+You can find the changelog here:
+https://github.com/apache/parquet-java/releases/tag/apache-parquet-<VERSION>-rc<NUM>
+
Binary artifacts are staged in Nexus here:
* https://repository.apache.org/content/groups/staging/org/apache/parquet/
@@ -48,16 +51,9 @@ Please vote in the next 72 hours.
[ ] +1 Release this as Apache Parquet <VERSION>
[ ] +0
[ ] -1 Do not release this because...
-</code></pre><h3 id=publishing-after-the-vote-passes>Publishing after the vote
passes</h3><p>After a release candidate passes a vote, the candidate needs to
be published as the final release.</p><h4
id=1-tag-final-release-and-set-development-version>1. Tag final release and set
development version</h4><pre><code>dev/finalize-release <release-version>
<rc-num> <new-development-version-without-SNAPSHOT-suffix>
-</code></pre><p>This will add the final release tag to the RC tag and sets the
new development version in the pom files. If everything is fine push the
changes and the new tag to github: <code>git push --follow-tags</code></p><h4
id=2-release-the-binary-repository-in-nexus>2. Release the binary repository in
Nexus</h4><p>Releasing a binary repository publishes the binaries to <a
href=https://repository.apache.org/content/groups/public/org/apache/parquet/>public</a>.</p><ol><li>Go
to <a h [...]
-cd parquet
-svn co https://dist.apache.org/repos/dist/dev/parquet candidates
-svn co https://dist.apache.org/repos/dist/release/parquet releases
-</code></pre><p>Next, copy the directory for the release candidate the passed
from candidates to releases and rename it; remove the “-rcN” part of the
directory name.</p><pre><code>cp -r
candidates/apache-parquet-<VERSION>-rcN/
releases/apache-parquet-<VERSION>
-</code></pre><p>Then add and commit the release artifacts:</p><pre><code>cd
releases
-svn add apache-parquet-<version>
-svn ci -m "Parquet: Add release <VERSION>"
-</code></pre><h4 id=4-update-parquetapacheorg>4. Update
parquet.apache.org</h4><p>Update the downloads page on parquet.apache.org.
Instructions for updating the site are on the <a
href=https://parquet.apache.org/docs/contribution-guidelines/contributing/>contribution
page</a>.</p><h4
id=5-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list>5.
Send an ANNOUNCE e-mail to <a
href=mailto:[email protected]>[email protected]</a> and the dev
list</h4><pre><c [...]
+</code></pre><h3 id=publishing-after-the-vote-passes>Publishing after the vote
passes</h3><p>After a release candidate passes a vote, the candidate needs to
be published as the final release.</p><h4
id=1-tag-final-release-and-set-development-version>1. Tag final release and set
development version</h4><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>./dev/finali [...]
+</span></span></code></pre></div><p>This will add the final release tag to the
RC tag and sets the new development version in the pom files. If everything is
fine push the changes and the new tag to GitHub: <code>git push
--follow-tags</code></p><h4 id=2-release-the-binary-repository-in-nexus>2.
Release the binary repository in Nexus</h4><p>Releasing a binary repository
publishes the binaries to <a
href=https://repository.apache.org/content/groups/public/org/apache/parquet/>public</a>.</
[...]
+</span></span></code></pre></div><h4 id=4-update-parquetapacheorg>4. Update
parquet.apache.org</h4><p>Update the downloads page on parquet.apache.org.
Instructions for updating the site are on the <a
href=https://parquet.apache.org/docs/contribution-guidelines/contributing/>contribution
page</a>.</p><h3 id=5-add-the-release-to-github>5. Add the release to
GitHub</h3><p>Add a <a
href=https://github.com/apache/parquet-java/releases/new>new release to
GitHub</a>. First select the newly tag [...]
I'm please to announce the release of Parquet <VERSION>!
@@ -66,7 +62,7 @@ Parquet is a general-purpose columnar file format for nested
data. It uses
space-efficient encodings and a compressed and splittable structure for
processing frameworks like Hadoop.
-Changes are listed at:
https://github.com/apache/parquet-mr/blob/apache-parquet-<VERSION>/CHANGES.md
+Changes are listed at:
https://github.com/apache/parquet-java/releases/tag/apache-parquet-<VERSION>
This release can be downloaded from: https://parquet.apache.org/downloads/
diff --git a/output/docs/contribution-guidelines/index.html
b/output/docs/contribution-guidelines/index.html
index 972742b..1aac4ca 100644
--- a/output/docs/contribution-guidelines/index.html
+++ b/output/docs/contribution-guidelines/index.html
@@ -7,6 +7,6 @@
<a
href=https://github.com/apache/parquet-site/edit/production/content/en/docs/Contribution%20Guidelines/_index.md
class="td-page-meta--edit td-page-meta__edit" target=_blank rel=noopener><i
class="fa-solid fa-pen-to-square fa-fw"></i> Edit this page</a>
<a
href="https://github.com/apache/parquet-site/new/production/content/en/docs/Contribution%20Guidelines?filename=change-me.md&value=---%0Atitle%3A+%22Long+Page+Title%22%0AlinkTitle%3A+%22Short+Nav+Title%22%0Aweight%3A+100%0Adescription%3A+%3E-%0A+++++Page+description+for+heading+and+indexes.%0A---%0A%0A%23%23+Heading%0A%0AEdit+this+template+to+create+your+new+page.%0A%0A%2A+Give+it+a+good+name%2C+ending+in+%60.md%60+-+e.g.+%60getting-started.md%60%0A%2A+Edit+the+%22front+matter%22+s
[...]
<a
href="https://github.com/apache/parquet-site/issues/new?title=Developer%20Guide";
class="td-page-meta--issue td-page-meta__issue" target=_blank rel=noopener><i
class="fa-solid fa-list-check fa-fw"></i> Create documentation issue</a>
-<a id=print href=/docs/contribution-guidelines/_print/><i class="fa-solid
fa-print fa-fw"></i> Print entire section</a></div></aside><main class="col-12
col-md-9 col-xl-8 ps-md-5" role=main><nav aria-label=breadcrumb
class=td-breadcrumbs><ol class=breadcrumb><li class=breadcrumb-item><a
href=/docs/>Documentation</a></li><li class="breadcrumb-item active"
aria-current=page>Developer Guide</li></ol></nav><div
class=td-content><h1>Developer Guide</h1><div class=lead>All developer
resources [...]
+<a id=print href=/docs/contribution-guidelines/_print/><i class="fa-solid
fa-print fa-fw"></i> Print entire section</a></div></aside><main class="col-12
col-md-9 col-xl-8 ps-md-5" role=main><nav aria-label=breadcrumb
class=td-breadcrumbs><ol class=breadcrumb><li class=breadcrumb-item><a
href=/docs/>Documentation</a></li><li class="breadcrumb-item active"
aria-current=page>Developer Guide</li></ol></nav><div
class=td-content><h1>Developer Guide</h1><div class=lead>All developer
resources [...]
2024
<span class=td-footer__authors>Apache Parquet</span></span><span
class=td-footer__all_rights_reserved>All Rights Reserved</span><span
class=ms-2><a href=https://policies.google.com/privacy target=_blank
rel=noopener>Privacy Policy</a></span></div></div></div></footer></div><script
src=/js/main.min.26b35480299b932e285af8358c943de97509b95a0086d091584e7cb9b00c5c7b.js
integrity="sha256-JrNUgCmbky4oWvg1jJQ96XUJuVoAhtCRWE58ubAMXHs="
crossorigin=anonymous></script><script defer src=/js/click-to [...]
\ No newline at end of file
diff --git a/output/docs/contribution-guidelines/index.xml
b/output/docs/contribution-guidelines/index.xml
index 9b45911..ed26f43 100644
--- a/output/docs/contribution-guidelines/index.xml
+++ b/output/docs/contribution-guidelines/index.xml
@@ -58,41 +58,32 @@ job in the <a
href="https://github.com/apache/parquet-site/blob/production/.g
</ol>
<p><strong>Do not directly edit the <code>asf-site</code> branch
of this repo</strong></p></description></item><item><title>Docs:
Releasing
Parquet</title><link>/docs/contribution-guidelines/releasing/</link><pubDate>Mon,
01 Jan 0001 00:00:00
+0000</pubDate><guid>/docs/contribution-guidelines/releasing/</guid><description>
<h3 id="setup">Setup</h3>
-<p>You will need: * PGP code signing keys, published in <a
href="https://downloads.apache.org/parquet/KEYS";>KEYS</a> * Permission to
stage artifacts in Nexus</p>
+<p>You will need:</p>
+<ul>
+<li>PGP code signing keys, published in <a
href="https://downloads.apache.org/parquet/KEYS";>KEYS</a>.</li>
+<li>Permission to stage artifacts in <a
href="https://repository.apache.org/";>Nexus</a>.</li>
+</ul>
<p>Make sure you have permission to deploy Parquet artifacts to Nexus by
pushing a snapshot:</p>
-<pre><code>mvn deploy
-</code></pre>
-<p>If you have problems, read the <a
href="https://www.apache.org/dev/publishing-maven-artifacts.html";>publishing
Maven artifacts documentation</a></p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span style="display:flex;"><span>mvn
deploy
+</span></span></code></pre></div><p>If you have problems,
read the <a
href="https://www.apache.org/dev/publishing-maven-artifacts.html";>publishing
Maven artifacts documentation</a>.</p>
<h3 id="release-process">Release process</h3>
<p>Parquet uses the maven-release-plugin to tag a release and push binary
artifacts to staging in Nexus. Once maven completes the release, the official
source tarball is built from the tag.</p>
<p>Before you start the release process:</p>
<ol>
-<li>Verify that the release is finished (no planned JIRAs are pending and
all patches are cherry-picked to the release branch)</li>
-<li>Resolve all associated JIRAs with correct target version and create the
next unreleased version in the JIRA project</li>
+<li>Verify that the release is finished (no planned Issues/PRs are pending
<a href="https://github.com/apache/parquet-java/milestones";>on the
milestone</a>)</li>
<li>Build and test the project</li>
-<li>Create a new branch for the release if this is a new minor version. For
example, if the new minor version is 1.13.0, create a new branch
<code>parquet-1.13.x</code></li>
-<li>Update the change log
-<ul>
-<li>Go to the release notes for the release in JIRA</li>
-<li>Copy the HTML and convert it to markdown with an <a
href="https://domchristie.github.io/turndown/";>online converter</a></li>
-<li>Add the content to CHANGES.md and update formatting</li>
-<li>Commit the update to CHANGES.md and make sure it is committed to both
release and master branches</li>
-</ul>
-</li>
+<li>Create a new branch for the release if this is a new minor version. For
example, if the new minor version is 1.14.0, create a new branch
<code>parquet-1.14.x</code></li>
</ol>
<h4 id="1-run-the-prepare-script">1. Run the prepare script</h4>
-<pre><code>dev/prepare-release.sh &lt;version&gt;
&lt;rc-number&gt;
-</code></pre>
-<p>This runs maven’s release prepare with a consistent tag name. After this
step, the release tag will exist in the git repository.</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>./dev/prepare-release.sh &lt;version&gt;
&lt;rc-number&gt;
+</span></span></code></pre></div><p>This runs maven’s
release prepare with a consistent tag name. After this step, the release tag
will exist in the git repository.</p>
<p>If this step fails, you can roll back the changes by running these
commands.</p>
-<pre><code>find ./ -type f -name '*.releaseBackup' -exec rm {} \;
-find ./ -type f -name 'pom.xml' -exec git checkout {} \;
-</code></pre>
-<h4 id="2-run-releaseperform-to-stage-binaries">2. Run release:perform to
stage binaries</h4>
-<pre><code>mvn release:perform
-</code></pre>
-<p>This uploads binary artifacts for the release tag to <a
href="https://repository.apache.org/";>Nexus</a>.</p>
-<h4 id="3-in-nexus-close-the-staging-repository">3. In Nexus, close the
staging repository</h4>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>find ./ -type f -name <span
style="color:#4e9a06">&#39;*.releaseBackup&#39;</span> -exec rm
<span style="color:#ce5c00;font-weight:bold">{}</span> <span
style="color:#4e9a06">\;</span>
+</span></span><span style="display:flex;"><span>find ./ -type f
-name <span style="color:#4e9a06">&#39;pom.xml&#39;</span> -exec
git checkout <span style="color:#ce5c00;font-weight:bold">{}</span>
<span style="color:#4e9a06">\;</span>
+</span></span></code></pre></div><h4
id="2-run-releaseperform-to-stage-binaries">2. Run release:perform to stage
binaries</h4>
+<p>Upload binary artifacts for the release tag to <a
href="https://repository.apache.org/";>Nexus</a>:</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span style="display:flex;"><span>mvn
release:perform
+</span></span></code></pre></div><h4
id="3-in-nexus-close-the-staging-repository">3. In Nexus, close the staging
repository</h4>
<p>Closing a staging repository makes the binaries available in <a
href="https://repository.apache.org/content/groups/staging/org/apache/parquet/";>staging</a>,
but does not publish them.</p>
<ol>
<li>Go to <a href="https://repository.apache.org/";>Nexus</a>.</li>
@@ -101,11 +92,12 @@ find ./ -type f -name 'pom.xml' -exec git checkout {} \;
<li>At the top, click “Close” and follow the instructions. For the comment
use “Apache Parquet [Format] ”.</li>
</ol>
<h4 id="4-run-the-source-tarball-script">4. Run the source tarball
script</h4>
-<pre><code>dev/source-release.sh &lt;version&gt;
&lt;rc-number&gt;
-</code></pre>
-<p>This script builds the source tarball from the release tag’s SHA1, signs
it, and uploads the necessary files with SVN.</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>dev/source-release.sh &lt;version&gt;
&lt;rc-number&gt;
+</span></span></code></pre></div><p>This script builds the
source tarball from the release tag’s SHA1, signs it, and uploads the necessary
files with SVN.</p>
<p>The source release is pushed to <a
href="https://dist.apache.org/repos/dist/dev/parquet/";>https://dist.apache.org/repos/dist/dev/parquet/</a></p>
<p>The last message from the script is the release commit’s SHA1 hash and
URL for the VOTE e-mail.</p>
+<h3 id="5-prepare-the-pre-release">5. Prepare the pre-release</h3>
+<p>Creating the <a
href="https://github.com/apache/parquet-java/releases/new";>pre-release</a>
will give the users the changelog to see if they need to validate certain
functionality. First select the newly created <code>rc</code> (ex:
<code>apache-parquet-1.15.0-rc0</code>) tag, and then the previous
release (ex. <code>apache-parquet-1.14.1</code>). Hit the
<code>Generate release notes</code> button to auto generate the notes.
You can curate the notes a b [...]
<h4
id="5-send-a-vote-e-mail-to-devparquetapacheorgmailtodevparquetapacheorg">5.
Send a VOTE e-mail to <a
href="mailto:[email protected]";>[email protected]</a></h4>
<p>Here is a template you can use. Make sure everything applies to your
release.</p>
<pre><code>Subject: [VOTE] Release Apache Parquet
&lt;VERSION&gt; RC&lt;NUM&gt;
@@ -118,6 +110,8 @@ The release tarball, signature, and checksums are here:
* https://dist.apache.org/repos/dist/dev/parquet/&lt;PATH&gt;
You can find the KEYS file here:
* https://downloads.apache.org/parquet/KEYS
+You can find the changelog here:
+https://github.com/apache/parquet-java/releases/tag/apache-parquet-&lt;VERSION&gt;-rc&lt;NUM&gt;
Binary artifacts are staged in Nexus here:
* https://repository.apache.org/content/groups/staging/org/apache/parquet/
This release includes important changes that I should have summarized here,
but I'm lazy.
@@ -130,9 +124,8 @@ Please vote in the next 72 hours.
<h3 id="publishing-after-the-vote-passes">Publishing after the vote
passes</h3>
<p>After a release candidate passes a vote, the candidate needs to be
published as the final release.</p>
<h4 id="1-tag-final-release-and-set-development-version">1. Tag final
release and set development version</h4>
-<pre><code>dev/finalize-release &lt;release-version&gt;
&lt;rc-num&gt;
&lt;new-development-version-without-SNAPSHOT-suffix&gt;
-</code></pre>
-<p>This will add the final release tag to the RC tag and sets the new
development version in the pom files. If everything is fine push the changes
and the new tag to github: <code>git push --follow-tags</code></p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>./dev/finalize-release
&lt;release-version&gt; &lt;rc-num&gt;
&lt;new-development-version-without-SNAPSHOT-suffix&gt;
+</span></span></code></pre></div><p>This will add the final
release tag to the RC tag and sets the new development version in the pom
files. If everything is fine push the changes and the new tag to GitHub:
<code>git push --follow-tags</code></p>
<h4 id="2-release-the-binary-repository-in-nexus">2. Release the binary
repository in Nexus</h4>
<p>Releasing a binary repository publishes the binaries to <a
href="https://repository.apache.org/content/groups/public/org/apache/parquet/";>public</a>.</p>
<ol>
@@ -143,28 +136,18 @@ Please vote in the next 72 hours.
</ol>
<h4 id="3-copy-the-release-artifacts-in-svn-into-releases">3. Copy the
release artifacts in SVN into releases</h4>
<p>First, check out the candidates and releases locations in SVN:</p>
-<pre><code>mkdir parquet
-cd parquet
-svn co https://dist.apache.org/repos/dist/dev/parquet candidates
-svn co https://dist.apache.org/repos/dist/release/parquet releases
-</code></pre>
-<p>Next, copy the directory for the release candidate the passed from
candidates to releases and rename it; remove the “-rcN” part of the directory
name.</p>
-<pre><code>cp -r candidates/apache-parquet-&lt;VERSION&gt;-rcN/
releases/apache-parquet-&lt;VERSION&gt;
-</code></pre>
-<p>Then add and commit the release artifacts:</p>
-<pre><code>cd releases
-svn add apache-parquet-&lt;version&gt;
-svn ci -m &quot;Parquet: Add release &lt;VERSION&gt;&quot;
-</code></pre>
-<h4 id="4-update-parquetapacheorg">4. Update parquet.apache.org</h4>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span style="display:flex;"><span>svn
mv
https://dist.apache.org/repos/dist/dev/parquet/apache-parquet-&lt;VERSION&gt;-rcN/
https://dist.apache.org/repos/dist/release/parquet/apache-parquet-&lt;VERSION&gt;
-m <span style="color:#4e9a06">&#34;Parquet: Add release
&lt;VERSION&gt;&#34;&l [...]
+</span></span></code></pre></div><h4
id="4-update-parquetapacheorg">4. Update parquet.apache.org</h4>
<p>Update the downloads page on parquet.apache.org. Instructions for
updating the site are on the <a
href="https://parquet.apache.org/docs/contribution-guidelines/contributing/";>contribution
page</a>.</p>
-<h4
id="5-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list">5.
Send an ANNOUNCE e-mail to <a
href="mailto:[email protected]";>[email protected]</a> and the dev
list</h4>
+<h3 id="5-add-the-release-to-github">5. Add the release to GitHub</h3>
+<p>Add a <a
href="https://github.com/apache/parquet-java/releases/new";>new release to
GitHub</a>. First select the newly tag (ex:
<code>apache-parquet-1.15.0</code>), and then the previous release (ex.
<code>apache-parquet-1.14.1</code>). You can copy the release notes from
the RC that passed the vote.</p>
+<h4
id="6-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list">6.
Send an ANNOUNCE e-mail to <a
href="mailto:[email protected]";>[email protected]</a> and the dev
list</h4>
<pre><code>[ANNOUNCE] Apache Parquet release &lt;VERSION&gt;
I'm please to announce the release of Parquet &lt;VERSION&gt;!
Parquet is a general-purpose columnar file format for nested data. It uses
space-efficient encodings and a compressed and splittable structure for
processing frameworks like Hadoop.
-Changes are listed at:
https://github.com/apache/parquet-mr/blob/apache-parquet-&lt;VERSION&gt;/CHANGES.md
+Changes are listed at:
https://github.com/apache/parquet-java/releases/tag/apache-parquet-&lt;VERSION&gt;
This release can be downloaded from: https://parquet.apache.org/downloads/
Java artifacts are available from Maven Central.
Thanks to everyone for contributing!
diff --git a/output/docs/contribution-guidelines/releasing/index.html
b/output/docs/contribution-guidelines/releasing/index.html
index 6ee5337..f3ec4c1 100644
--- a/output/docs/contribution-guidelines/releasing/index.html
+++ b/output/docs/contribution-guidelines/releasing/index.html
@@ -1,19 +1,19 @@
<!doctype html><html itemscope itemtype=http://schema.org/WebPage lang=en
class=no-js><head><meta charset=utf-8><meta name=viewport
content="width=device-width,initial-scale=1,shrink-to-fit=no"><meta name=robots
content="index, follow"><link rel="shortcut icon"
href=/favicons/favicon.ico><link rel=apple-touch-icon
href=/favicons/apple-touch-icon-180x180.png sizes=180x180><link rel=icon
type=image/png href=/favicons/favicon-16x16.png sizes=16x16><link rel=icon
type=image/png href=/favicon [...]
-<meta name=description content="How to release Parquet
-"><meta property="og:title" content="Releasing Parquet"><meta
property="og:description" content="How to release Parquet
-"><meta property="og:type" content="article"><meta property="og:url"
content="/docs/contribution-guidelines/releasing/"><meta
property="article:section" content="docs"><meta
property="article:modified_time" content="2024-03-11T22:11:10+01:00"><meta
property="og:site_name" content="Apache Parquet"><meta itemprop=name
content="Releasing Parquet"><meta itemprop=description content="How to release
Parquet
-"><meta itemprop=dateModified content="2024-03-11T22:11:10+01:00"><meta
itemprop=wordCount content="822"><meta itemprop=keywords content><meta
name=twitter:card content="summary"><meta name=twitter:title content="Releasing
Parquet"><meta name=twitter:description content="How to release Parquet
+<meta name=description content="How to release Parquet-Java
+"><meta property="og:title" content="Releasing Parquet"><meta
property="og:description" content="How to release Parquet-Java
+"><meta property="og:type" content="article"><meta property="og:url"
content="/docs/contribution-guidelines/releasing/"><meta
property="article:section" content="docs"><meta
property="article:modified_time" content="2024-08-06T11:29:49+02:00"><meta
property="og:site_name" content="Apache Parquet"><meta itemprop=name
content="Releasing Parquet"><meta itemprop=description content="How to release
Parquet-Java
+"><meta itemprop=dateModified content="2024-08-06T11:29:49+02:00"><meta
itemprop=wordCount content="826"><meta itemprop=keywords content><meta
name=twitter:card content="summary"><meta name=twitter:title content="Releasing
Parquet"><meta name=twitter:description content="How to release Parquet-Java
"><link rel=preload
href=/scss/main.min.7f095589dcf99af199766009c9a9719e6fdf2b9ce9bcfbeb05e80eb6efeaf32b.css
as=style><link
href=/scss/main.min.7f095589dcf99af199766009c9a9719e6fdf2b9ce9bcfbeb05e80eb6efeaf32b.css
rel=stylesheet integrity><script
src=https://code.jquery.com/jquery-3.6.3.min.js
integrity="sha512-STof4xm1wgkfm7heWqFJVn58Hm3EtS31XFaagaa8VMReCXAkQnJZ+jEy8PCC/iT18dFy95WcExNHFTqLyp72eQ=="
crossorigin=anonymous></script><link rel=stylesheet
href=https://cdn.jsdelivr.net/npm/@doc [...]
<a
href=https://github.com/apache/parquet-site/edit/production/content/en/docs/Contribution%20Guidelines/releasing.md
class="td-page-meta--edit td-page-meta__edit" target=_blank rel=noopener><i
class="fa-solid fa-pen-to-square fa-fw"></i> Edit this page</a>
<a
href="https://github.com/apache/parquet-site/new/production/content/en/docs/Contribution%20Guidelines?filename=change-me.md&value=---%0Atitle%3A+%22Long+Page+Title%22%0AlinkTitle%3A+%22Short+Nav+Title%22%0Aweight%3A+100%0Adescription%3A+%3E-%0A+++++Page+description+for+heading+and+indexes.%0A---%0A%0A%23%23+Heading%0A%0AEdit+this+template+to+create+your+new+page.%0A%0A%2A+Give+it+a+good+name%2C+ending+in+%60.md%60+-+e.g.+%60getting-started.md%60%0A%2A+Edit+the+%22front+matter%22+s
[...]
<a
href="https://github.com/apache/parquet-site/issues/new?title=Releasing%20Parquet";
class="td-page-meta--issue td-page-meta__issue" target=_blank rel=noopener><i
class="fa-solid fa-list-check fa-fw"></i> Create documentation issue</a>
-<a id=print href=/docs/contribution-guidelines/_print/><i class="fa-solid
fa-print fa-fw"></i> Print entire section</a></div><div class=td-toc><nav
id=TableOfContents><ul><li><ul><li><a href=#setup>Setup</a></li><li><a
href=#release-process>Release process</a></li><li><a
href=#publishing-after-the-vote-passes>Publishing after the vote
passes</a></li></ul></li></ul></nav></div></aside><main class="col-12 col-md-9
col-xl-8 ps-md-5" role=main><nav aria-label=breadcrumb class=td-breadcrumbs>
[...]
-</code></pre><p>If you have problems, read the <a
href=https://www.apache.org/dev/publishing-maven-artifacts.html>publishing
Maven artifacts documentation</a></p><h3 id=release-process>Release
process</h3><p>Parquet uses the maven-release-plugin to tag a release and push
binary artifacts to staging in Nexus. Once maven completes the release, the
official source tarball is built from the tag.</p><p>Before you start the
release process:</p><ol><li>Verify that the release is finished (no pl [...]
-</code></pre><p>This runs maven’s release prepare with a consistent tag name.
After this step, the release tag will exist in the git repository.</p><p>If
this step fails, you can roll back the changes by running these
commands.</p><pre><code>find ./ -type f -name '*.releaseBackup' -exec rm {} \;
-find ./ -type f -name 'pom.xml' -exec git checkout {} \;
-</code></pre><h4 id=2-run-releaseperform-to-stage-binaries>2. Run
release:perform to stage binaries</h4><pre><code>mvn release:perform
-</code></pre><p>This uploads binary artifacts for the release tag to <a
href=https://repository.apache.org/>Nexus</a>.</p><h4
id=3-in-nexus-close-the-staging-repository>3. In Nexus, close the staging
repository</h4><p>Closing a staging repository makes the binaries available in
<a
href=https://repository.apache.org/content/groups/staging/org/apache/parquet/>staging</a>,
but does not publish them.</p><ol><li>Go to <a
href=https://repository.apache.org/>Nexus</a>.</li><li>In the menu on th [...]
-</code></pre><p>This script builds the source tarball from the release tag’s
SHA1, signs it, and uploads the necessary files with SVN.</p><p>The source
release is pushed to <a
href=https://dist.apache.org/repos/dist/dev/parquet/>https://dist.apache.org/repos/dist/dev/parquet/</a></p><p>The
last message from the script is the release commit’s SHA1 hash and URL for the
VOTE e-mail.</p><h4
id=5-send-a-vote-e-mail-to-devparquetapacheorgmailtodevparquetapacheorg>5. Send
a VOTE e-mail to <a hr [...]
+<a id=print href=/docs/contribution-guidelines/_print/><i class="fa-solid
fa-print fa-fw"></i> Print entire section</a></div><div class=td-toc><nav
id=TableOfContents><ul><li><ul><li><a href=#setup>Setup</a></li><li><a
href=#release-process>Release process</a></li><li><a
href=#5-prepare-the-pre-release>5. Prepare the pre-release</a></li><li><a
href=#publishing-after-the-vote-passes>Publishing after the vote
passes</a></li><li><a href=#5-add-the-release-to-github>5. Add the release to
Git [...]
+</span></span></code></pre></div><p>If you have problems, read the <a
href=https://www.apache.org/dev/publishing-maven-artifacts.html>publishing
Maven artifacts documentation</a>.</p><h3 id=release-process>Release
process</h3><p>Parquet uses the maven-release-plugin to tag a release and push
binary artifacts to staging in Nexus. Once maven completes the release, the
official source tarball is built from the tag.</p><p>Before you start the
release process:</p><ol><li>Verify that the relea [...]
+</span></span></code></pre></div><p>This runs maven’s release prepare with a
consistent tag name. After this step, the release tag will exist in the git
repository.</p><p>If this step fails, you can roll back the changes by running
these commands.</p><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>find ./ -type f
-name <span style=color:#4e9a06>'*.releaseBa [...]
+</span></span><span style=display:flex><span>find ./ -type f -name <span
style=color:#4e9a06>'pom.xml'</span> -exec git checkout <span
style=color:#ce5c00;font-weight:700>{}</span> <span
style=color:#4e9a06>\;</span>
+</span></span></code></pre></div><h4
id=2-run-releaseperform-to-stage-binaries>2. Run release:perform to stage
binaries</h4><p>Upload binary artifacts for the release tag to <a
href=https://repository.apache.org/>Nexus</a>:</p><div class=highlight><pre
tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>mvn
release:perform
+</span></span></code></pre></div><h4
id=3-in-nexus-close-the-staging-repository>3. In Nexus, close the staging
repository</h4><p>Closing a staging repository makes the binaries available in
<a
href=https://repository.apache.org/content/groups/staging/org/apache/parquet/>staging</a>,
but does not publish them.</p><ol><li>Go to <a
href=https://repository.apache.org/>Nexus</a>.</li><li>In the menu on the left,
choose “Staging Repositories”.</li><li>Select the Parquet
repository.</li><li>At [...]
+</span></span></code></pre></div><p>This script builds the source tarball from
the release tag’s SHA1, signs it, and uploads the necessary files with
SVN.</p><p>The source release is pushed to <a
href=https://dist.apache.org/repos/dist/dev/parquet/>https://dist.apache.org/repos/dist/dev/parquet/</a></p><p>The
last message from the script is the release commit’s SHA1 hash and URL for the
VOTE e-mail.</p><h3 id=5-prepare-the-pre-release>5. Prepare the
pre-release</h3><p>Creating the <a hre [...]
Hi everyone,
@@ -30,6 +30,9 @@ The release tarball, signature, and checksums are here:
You can find the KEYS file here:
* https://downloads.apache.org/parquet/KEYS
+You can find the changelog here:
+https://github.com/apache/parquet-java/releases/tag/apache-parquet-<VERSION>-rc<NUM>
+
Binary artifacts are staged in Nexus here:
* https://repository.apache.org/content/groups/staging/org/apache/parquet/
@@ -42,16 +45,9 @@ Please vote in the next 72 hours.
[ ] +1 Release this as Apache Parquet <VERSION>
[ ] +0
[ ] -1 Do not release this because...
-</code></pre><h3 id=publishing-after-the-vote-passes>Publishing after the vote
passes</h3><p>After a release candidate passes a vote, the candidate needs to
be published as the final release.</p><h4
id=1-tag-final-release-and-set-development-version>1. Tag final release and set
development version</h4><pre><code>dev/finalize-release <release-version>
<rc-num> <new-development-version-without-SNAPSHOT-suffix>
-</code></pre><p>This will add the final release tag to the RC tag and sets the
new development version in the pom files. If everything is fine push the
changes and the new tag to github: <code>git push --follow-tags</code></p><h4
id=2-release-the-binary-repository-in-nexus>2. Release the binary repository in
Nexus</h4><p>Releasing a binary repository publishes the binaries to <a
href=https://repository.apache.org/content/groups/public/org/apache/parquet/>public</a>.</p><ol><li>Go
to <a h [...]
-cd parquet
-svn co https://dist.apache.org/repos/dist/dev/parquet candidates
-svn co https://dist.apache.org/repos/dist/release/parquet releases
-</code></pre><p>Next, copy the directory for the release candidate the passed
from candidates to releases and rename it; remove the “-rcN” part of the
directory name.</p><pre><code>cp -r
candidates/apache-parquet-<VERSION>-rcN/
releases/apache-parquet-<VERSION>
-</code></pre><p>Then add and commit the release artifacts:</p><pre><code>cd
releases
-svn add apache-parquet-<version>
-svn ci -m "Parquet: Add release <VERSION>"
-</code></pre><h4 id=4-update-parquetapacheorg>4. Update
parquet.apache.org</h4><p>Update the downloads page on parquet.apache.org.
Instructions for updating the site are on the <a
href=https://parquet.apache.org/docs/contribution-guidelines/contributing/>contribution
page</a>.</p><h4
id=5-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list>5.
Send an ANNOUNCE e-mail to <a
href=mailto:[email protected]>[email protected]</a> and the dev
list</h4><pre><c [...]
+</code></pre><h3 id=publishing-after-the-vote-passes>Publishing after the vote
passes</h3><p>After a release candidate passes a vote, the candidate needs to
be published as the final release.</p><h4
id=1-tag-final-release-and-set-development-version>1. Tag final release and set
development version</h4><div class=highlight><pre tabindex=0
style=background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4><code
class=language-sh data-lang=sh><span style=display:flex><span>./dev/finali [...]
+</span></span></code></pre></div><p>This will add the final release tag to the
RC tag and sets the new development version in the pom files. If everything is
fine push the changes and the new tag to GitHub: <code>git push
--follow-tags</code></p><h4 id=2-release-the-binary-repository-in-nexus>2.
Release the binary repository in Nexus</h4><p>Releasing a binary repository
publishes the binaries to <a
href=https://repository.apache.org/content/groups/public/org/apache/parquet/>public</a>.</
[...]
+</span></span></code></pre></div><h4 id=4-update-parquetapacheorg>4. Update
parquet.apache.org</h4><p>Update the downloads page on parquet.apache.org.
Instructions for updating the site are on the <a
href=https://parquet.apache.org/docs/contribution-guidelines/contributing/>contribution
page</a>.</p><h3 id=5-add-the-release-to-github>5. Add the release to
GitHub</h3><p>Add a <a
href=https://github.com/apache/parquet-java/releases/new>new release to
GitHub</a>. First select the newly tag [...]
I'm please to announce the release of Parquet <VERSION>!
@@ -60,13 +56,13 @@ Parquet is a general-purpose columnar file format for
nested data. It uses
space-efficient encodings and a compressed and splittable structure for
processing frameworks like Hadoop.
-Changes are listed at:
https://github.com/apache/parquet-mr/blob/apache-parquet-<VERSION>/CHANGES.md
+Changes are listed at:
https://github.com/apache/parquet-java/releases/tag/apache-parquet-<VERSION>
This release can be downloaded from: https://parquet.apache.org/downloads/
Java artifacts are available from Maven Central.
Thanks to everyone for contributing!
-</code></pre><div class=td-page-meta__lastmod>Last modified March 11, 2024: <a
href=https://github.com/apache/parquet-site/commit/e79b30489c6bd50f0829a5f2b87f4a26f5e4af05>Fix
typos (#46) (e79b304)</a></div></div></main></div></div><footer
class="td-footer row d-print-none"><div class=container-fluid><div class="row
mx-md-2"><div class="td-footer__left col-6 col-sm-4 order-sm-1"><ul
class=td-footer__links-list><li class=td-footer__links-item
data-bs-toggle=tooltip title="Post to Mailing L [...]
+</code></pre><div class=td-page-meta__lastmod>Last modified August 6, 2024: <a
href=https://github.com/apache/parquet-site/commit/de8fc26563951c0d47bc8f157bacf9c64fe3e012>Update
`releases.md` (#78) (de8fc26)</a></div></div></main></div></div><footer
class="td-footer row d-print-none"><div class=container-fluid><div class="row
mx-md-2"><div class="td-footer__left col-6 col-sm-4 order-sm-1"><ul
class=td-footer__links-list><li class=td-footer__links-item
data-bs-toggle=tooltip title="Post t [...]
2024
<span class=td-footer__authors>Apache Parquet</span></span><span
class=td-footer__all_rights_reserved>All Rights Reserved</span><span
class=ms-2><a href=https://policies.google.com/privacy target=_blank
rel=noopener>Privacy Policy</a></span></div></div></div></footer></div><script
src=/js/main.min.26b35480299b932e285af8358c943de97509b95a0086d091584e7cb9b00c5c7b.js
integrity="sha256-JrNUgCmbky4oWvg1jJQ96XUJuVoAhtCRWE58ubAMXHs="
crossorigin=anonymous></script><script defer src=/js/click-to [...]
\ No newline at end of file
diff --git a/output/docs/index.xml b/output/docs/index.xml
index b934d79..52a5dbb 100644
--- a/output/docs/index.xml
+++ b/output/docs/index.xml
@@ -916,41 +916,32 @@ job in the <a
href="https://github.com/apache/parquet-site/blob/production/.g
<p><a
href="https://www.apache.org/foundation/thanks.html";>Sponsor</a></p></description></item><item><title>Docs:
Donate</title><link>/docs/asf/donate/</link><pubDate>Mon, 01 Jan 0001 00:00:00
+0000</pubDate><guid>/docs/asf/donate/</guid><description>
<p><a
href="https://www.apache.org/foundation/sponsorship.html";>Donate</a></p></description></item><item><title>Docs:
Releasing
Parquet</title><link>/docs/contribution-guidelines/releasing/</link><pubDate>Mon,
01 Jan 0001 00:00:00
+0000</pubDate><guid>/docs/contribution-guidelines/releasing/</guid><description>
<h3 id="setup">Setup</h3>
-<p>You will need: * PGP code signing keys, published in <a
href="https://downloads.apache.org/parquet/KEYS";>KEYS</a> * Permission to
stage artifacts in Nexus</p>
+<p>You will need:</p>
+<ul>
+<li>PGP code signing keys, published in <a
href="https://downloads.apache.org/parquet/KEYS";>KEYS</a>.</li>
+<li>Permission to stage artifacts in <a
href="https://repository.apache.org/";>Nexus</a>.</li>
+</ul>
<p>Make sure you have permission to deploy Parquet artifacts to Nexus by
pushing a snapshot:</p>
-<pre><code>mvn deploy
-</code></pre>
-<p>If you have problems, read the <a
href="https://www.apache.org/dev/publishing-maven-artifacts.html";>publishing
Maven artifacts documentation</a></p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span style="display:flex;"><span>mvn
deploy
+</span></span></code></pre></div><p>If you have problems,
read the <a
href="https://www.apache.org/dev/publishing-maven-artifacts.html";>publishing
Maven artifacts documentation</a>.</p>
<h3 id="release-process">Release process</h3>
<p>Parquet uses the maven-release-plugin to tag a release and push binary
artifacts to staging in Nexus. Once maven completes the release, the official
source tarball is built from the tag.</p>
<p>Before you start the release process:</p>
<ol>
-<li>Verify that the release is finished (no planned JIRAs are pending and
all patches are cherry-picked to the release branch)</li>
-<li>Resolve all associated JIRAs with correct target version and create the
next unreleased version in the JIRA project</li>
+<li>Verify that the release is finished (no planned Issues/PRs are pending
<a href="https://github.com/apache/parquet-java/milestones";>on the
milestone</a>)</li>
<li>Build and test the project</li>
-<li>Create a new branch for the release if this is a new minor version. For
example, if the new minor version is 1.13.0, create a new branch
<code>parquet-1.13.x</code></li>
-<li>Update the change log
-<ul>
-<li>Go to the release notes for the release in JIRA</li>
-<li>Copy the HTML and convert it to markdown with an <a
href="https://domchristie.github.io/turndown/";>online converter</a></li>
-<li>Add the content to CHANGES.md and update formatting</li>
-<li>Commit the update to CHANGES.md and make sure it is committed to both
release and master branches</li>
-</ul>
-</li>
+<li>Create a new branch for the release if this is a new minor version. For
example, if the new minor version is 1.14.0, create a new branch
<code>parquet-1.14.x</code></li>
</ol>
<h4 id="1-run-the-prepare-script">1. Run the prepare script</h4>
-<pre><code>dev/prepare-release.sh &lt;version&gt;
&lt;rc-number&gt;
-</code></pre>
-<p>This runs maven’s release prepare with a consistent tag name. After this
step, the release tag will exist in the git repository.</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>./dev/prepare-release.sh &lt;version&gt;
&lt;rc-number&gt;
+</span></span></code></pre></div><p>This runs maven’s
release prepare with a consistent tag name. After this step, the release tag
will exist in the git repository.</p>
<p>If this step fails, you can roll back the changes by running these
commands.</p>
-<pre><code>find ./ -type f -name '*.releaseBackup' -exec rm {} \;
-find ./ -type f -name 'pom.xml' -exec git checkout {} \;
-</code></pre>
-<h4 id="2-run-releaseperform-to-stage-binaries">2. Run release:perform to
stage binaries</h4>
-<pre><code>mvn release:perform
-</code></pre>
-<p>This uploads binary artifacts for the release tag to <a
href="https://repository.apache.org/";>Nexus</a>.</p>
-<h4 id="3-in-nexus-close-the-staging-repository">3. In Nexus, close the
staging repository</h4>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>find ./ -type f -name <span
style="color:#4e9a06">&#39;*.releaseBackup&#39;</span> -exec rm
<span style="color:#ce5c00;font-weight:bold">{}</span> <span
style="color:#4e9a06">\;</span>
+</span></span><span style="display:flex;"><span>find ./ -type f
-name <span style="color:#4e9a06">&#39;pom.xml&#39;</span> -exec
git checkout <span style="color:#ce5c00;font-weight:bold">{}</span>
<span style="color:#4e9a06">\;</span>
+</span></span></code></pre></div><h4
id="2-run-releaseperform-to-stage-binaries">2. Run release:perform to stage
binaries</h4>
+<p>Upload binary artifacts for the release tag to <a
href="https://repository.apache.org/";>Nexus</a>:</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span style="display:flex;"><span>mvn
release:perform
+</span></span></code></pre></div><h4
id="3-in-nexus-close-the-staging-repository">3. In Nexus, close the staging
repository</h4>
<p>Closing a staging repository makes the binaries available in <a
href="https://repository.apache.org/content/groups/staging/org/apache/parquet/";>staging</a>,
but does not publish them.</p>
<ol>
<li>Go to <a href="https://repository.apache.org/";>Nexus</a>.</li>
@@ -959,11 +950,12 @@ find ./ -type f -name 'pom.xml' -exec git checkout {} \;
<li>At the top, click “Close” and follow the instructions. For the comment
use “Apache Parquet [Format] ”.</li>
</ol>
<h4 id="4-run-the-source-tarball-script">4. Run the source tarball
script</h4>
-<pre><code>dev/source-release.sh &lt;version&gt;
&lt;rc-number&gt;
-</code></pre>
-<p>This script builds the source tarball from the release tag’s SHA1, signs
it, and uploads the necessary files with SVN.</p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>dev/source-release.sh &lt;version&gt;
&lt;rc-number&gt;
+</span></span></code></pre></div><p>This script builds the
source tarball from the release tag’s SHA1, signs it, and uploads the necessary
files with SVN.</p>
<p>The source release is pushed to <a
href="https://dist.apache.org/repos/dist/dev/parquet/";>https://dist.apache.org/repos/dist/dev/parquet/</a></p>
<p>The last message from the script is the release commit’s SHA1 hash and
URL for the VOTE e-mail.</p>
+<h3 id="5-prepare-the-pre-release">5. Prepare the pre-release</h3>
+<p>Creating the <a
href="https://github.com/apache/parquet-java/releases/new";>pre-release</a>
will give the users the changelog to see if they need to validate certain
functionality. First select the newly created <code>rc</code> (ex:
<code>apache-parquet-1.15.0-rc0</code>) tag, and then the previous
release (ex. <code>apache-parquet-1.14.1</code>). Hit the
<code>Generate release notes</code> button to auto generate the notes.
You can curate the notes a b [...]
<h4
id="5-send-a-vote-e-mail-to-devparquetapacheorgmailtodevparquetapacheorg">5.
Send a VOTE e-mail to <a
href="mailto:[email protected]";>[email protected]</a></h4>
<p>Here is a template you can use. Make sure everything applies to your
release.</p>
<pre><code>Subject: [VOTE] Release Apache Parquet
&lt;VERSION&gt; RC&lt;NUM&gt;
@@ -976,6 +968,8 @@ The release tarball, signature, and checksums are here:
* https://dist.apache.org/repos/dist/dev/parquet/&lt;PATH&gt;
You can find the KEYS file here:
* https://downloads.apache.org/parquet/KEYS
+You can find the changelog here:
+https://github.com/apache/parquet-java/releases/tag/apache-parquet-&lt;VERSION&gt;-rc&lt;NUM&gt;
Binary artifacts are staged in Nexus here:
* https://repository.apache.org/content/groups/staging/org/apache/parquet/
This release includes important changes that I should have summarized here,
but I'm lazy.
@@ -988,9 +982,8 @@ Please vote in the next 72 hours.
<h3 id="publishing-after-the-vote-passes">Publishing after the vote
passes</h3>
<p>After a release candidate passes a vote, the candidate needs to be
published as the final release.</p>
<h4 id="1-tag-final-release-and-set-development-version">1. Tag final
release and set development version</h4>
-<pre><code>dev/finalize-release &lt;release-version&gt;
&lt;rc-num&gt;
&lt;new-development-version-without-SNAPSHOT-suffix&gt;
-</code></pre>
-<p>This will add the final release tag to the RC tag and sets the new
development version in the pom files. If everything is fine push the changes
and the new tag to github: <code>git push --follow-tags</code></p>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span
style="display:flex;"><span>./dev/finalize-release
&lt;release-version&gt; &lt;rc-num&gt;
&lt;new-development-version-without-SNAPSHOT-suffix&gt;
+</span></span></code></pre></div><p>This will add the final
release tag to the RC tag and sets the new development version in the pom
files. If everything is fine push the changes and the new tag to GitHub:
<code>git push --follow-tags</code></p>
<h4 id="2-release-the-binary-repository-in-nexus">2. Release the binary
repository in Nexus</h4>
<p>Releasing a binary repository publishes the binaries to <a
href="https://repository.apache.org/content/groups/public/org/apache/parquet/";>public</a>.</p>
<ol>
@@ -1001,28 +994,18 @@ Please vote in the next 72 hours.
</ol>
<h4 id="3-copy-the-release-artifacts-in-svn-into-releases">3. Copy the
release artifacts in SVN into releases</h4>
<p>First, check out the candidates and releases locations in SVN:</p>
-<pre><code>mkdir parquet
-cd parquet
-svn co https://dist.apache.org/repos/dist/dev/parquet candidates
-svn co https://dist.apache.org/repos/dist/release/parquet releases
-</code></pre>
-<p>Next, copy the directory for the release candidate the passed from
candidates to releases and rename it; remove the “-rcN” part of the directory
name.</p>
-<pre><code>cp -r candidates/apache-parquet-&lt;VERSION&gt;-rcN/
releases/apache-parquet-&lt;VERSION&gt;
-</code></pre>
-<p>Then add and commit the release artifacts:</p>
-<pre><code>cd releases
-svn add apache-parquet-&lt;version&gt;
-svn ci -m &quot;Parquet: Add release &lt;VERSION&gt;&quot;
-</code></pre>
-<h4 id="4-update-parquetapacheorg">4. Update parquet.apache.org</h4>
+<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-sh" data-lang="sh"><span style="display:flex;"><span>svn
mv
https://dist.apache.org/repos/dist/dev/parquet/apache-parquet-&lt;VERSION&gt;-rcN/
https://dist.apache.org/repos/dist/release/parquet/apache-parquet-&lt;VERSION&gt;
-m <span style="color:#4e9a06">&#34;Parquet: Add release
&lt;VERSION&gt;&#34;&l [...]
+</span></span></code></pre></div><h4
id="4-update-parquetapacheorg">4. Update parquet.apache.org</h4>
<p>Update the downloads page on parquet.apache.org. Instructions for
updating the site are on the <a
href="https://parquet.apache.org/docs/contribution-guidelines/contributing/";>contribution
page</a>.</p>
-<h4
id="5-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list">5.
Send an ANNOUNCE e-mail to <a
href="mailto:[email protected]";>[email protected]</a> and the dev
list</h4>
+<h3 id="5-add-the-release-to-github">5. Add the release to GitHub</h3>
+<p>Add a <a
href="https://github.com/apache/parquet-java/releases/new";>new release to
GitHub</a>. First select the newly tag (ex:
<code>apache-parquet-1.15.0</code>), and then the previous release (ex.
<code>apache-parquet-1.14.1</code>). You can copy the release notes from
the RC that passed the vote.</p>
+<h4
id="6-send-an-announce-e-mail-to-announceapacheorgmailtoannounceapacheorg-and-the-dev-list">6.
Send an ANNOUNCE e-mail to <a
href="mailto:[email protected]";>[email protected]</a> and the dev
list</h4>
<pre><code>[ANNOUNCE] Apache Parquet release &lt;VERSION&gt;
I'm please to announce the release of Parquet &lt;VERSION&gt;!
Parquet is a general-purpose columnar file format for nested data. It uses
space-efficient encodings and a compressed and splittable structure for
processing frameworks like Hadoop.
-Changes are listed at:
https://github.com/apache/parquet-mr/blob/apache-parquet-&lt;VERSION&gt;/CHANGES.md
+Changes are listed at:
https://github.com/apache/parquet-java/releases/tag/apache-parquet-&lt;VERSION&gt;
This release can be downloaded from: https://parquet.apache.org/downloads/
Java artifacts are available from Maven Central.
Thanks to everyone for contributing!
diff --git a/output/sitemap.xml b/output/sitemap.xml
index fc08463..ca136f1 100644
--- a/output/sitemap.xml
+++ b/output/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/file-format/data-pages/compression/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encodings/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encryption/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/
[...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/docs/file-format/data-pages/compression/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encodings/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/file-format/data-pages/encryption/</loc><lastmod>2024-03-11T22:11:10+01:00</lastmod></url><url><loc>/docs/
[...]
\ No newline at end of file
