This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/celix-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f24a0b2 Updated site from master
(0413724ec5b8fdaa075776aabcf6a856a9b5cd61)
f24a0b2 is described below
commit f24a0b20f6ea6d8d9852580a9375307bfadbda43
Author: jenkins <[email protected]>
AuthorDate: Tue Jul 26 20:47:46 2022 +0000
Updated site from master (0413724ec5b8fdaa075776aabcf6a856a9b5cd61)
---
content/contributing/releasing.html | 14 ++++++++------
content/sitemap.xml | 6 +++---
2 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/content/contributing/releasing.html
b/content/contributing/releasing.html
index 2725848..f3f231f 100644
--- a/content/contributing/releasing.html
+++ b/content/contributing/releasing.html
@@ -158,11 +158,11 @@ of these keys can be found on the <a
href="https://www.apache.org/dev/release-si
and <a href="https://www.apache.org/dev/openpgp.html#generate-key";>How To
OpenPGP</a>. Be sure to follow the information
provided on that site and its references.</p>
<p>The generated key can be uploaded to the <a href="https://pgp.mit.edu/";>MIT
PGP Public Key Server</a>.</p>
-<p>Next, the public key signature must be added to the KEYS file. Again, read
the <a
href="https://www.apache.org/dev/release-signing.html#keys-policy";>Signing
Releases page</a>
-for more information. This updated file needs to be uploaded to GIT, be sure
to upload it to:</p>
+<p>Next, the public key signature must be added to the <a
href="https://downloads.apache.org/celix/KEYS";>Celix KEYS file</a>.
+Again, read the <a
href="https://www.apache.org/dev/release-signing.html#keys-policy";>Signing
Releases page</a> for more
+information. This updated file needs to be uploaded to SVN at the following
location:</p>
<ul>
-<li><a href="https://dist.apache.org/repos/dist/dev/celix/KEYS";>Apache Celix
release development area KEYS</a></li>
-<li><a href="https://downloads.apache.org/celix/KEYS";>Apache Celix release
distribution area KEYS</a></li>
+<li><a href="https://dist.apache.org/repos/dist/release/celix/KEYS";>Apache
Celix release distribution area KEYS</a></li>
</ul>
<h2 id="create-release-branch">Create release branch</h2>
<p>A release will be prepared in a release branch. This branch is created from
the <code>master</code> branch.</p>
@@ -233,8 +233,8 @@ $ make rat
the rat-excludes.txt file in the root of the project. Be sure it is a false
positive! If in doubt, ask the mailing list! Third party
licenses may need to be mentioned in the NOTICE file.</p>
<h2 id="create-sign-and-publish-artifacts">Create, sign and publish
artifacts</h2>
-<p>Since Celix only releases source artifacts, creating the artifact is simple
and straightforward
-First verify that all changes are committed to the release branch and the
branch is pushed to github</p>
+<p>Since Celix only releases source artifacts, creating the artifact is simple
and straightforward.
+First verify that all changes are committed to the release branch and the
branch is pushed to GitHub.</p>
<div class="highlight"><pre
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4"><code
class="language-bash" data-lang="bash"><span
style="color:#080;font-style:italic"># Create symbolic link so the archive has
a directory with version information</span>
$ ln -s celix celix-X.Y.Z
@@ -366,6 +366,8 @@
https://github.com/apache/celix-site/blob/master/layouts/partials/header.html";>h
https://github.com/apache/celix-site/blob/master/extract_celix_docs.sh";>extract_celix_docs.sh</a>
script to copy the markdown documentation within the Celix code base
to the website.</li>
<li>Verify whether the documentation is correctly copied & otherwise make
some minor tweaks.</li>
+<li>Create a <code>docs.md</code> file within the release documentation
directory (example path: <code>source/docs/2.2.1/docs.md</code>, where 2.2.1
needs to be
+substituted with the actual released version). This file can be copied and
updated from e.g. a previous release.</li>
<li>Check-in the documentation and create a pull request to the <a
href="https://github.com/apache/celix-site";>celix-site</a> repository for the
Celix team to review.</li>
</ul>
<p>Once the site is updated proceed with announcing the release.</p>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index f4a14ee..ded9bc5 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -4,7 +4,7 @@
<url>
<loc>https://celix.apache.org/</loc>
- <lastmod>2022-07-11T14:13:05+08:00</lastmod>
+ <lastmod>2022-07-17T19:58:57+02:00</lastmod>
</url>
<url>
@@ -109,7 +109,7 @@
<url>
<loc>https://celix.apache.org/contributing.html</loc>
- <lastmod>2022-07-11T14:13:05+08:00</lastmod>
+ <lastmod>2022-07-17T19:58:57+02:00</lastmod>
</url>
<url>
@@ -334,7 +334,7 @@
<url>
<loc>https://celix.apache.org/contributing/releasing.html</loc>
- <lastmod>2021-04-18T15:01:01+02:00</lastmod>
+ <lastmod>2022-07-17T19:58:57+02:00</lastmod>
</url>
<url>
