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 a47ff25 Updated site from master
(aaaf48174b244d7d54ef9b8b0b6547a75c7482e8)
a47ff25 is described below
commit a47ff250b9f483d0236ef789ce6621d3ab0b4cbf
Author: jenkins <[email protected]>
AuthorDate: Sat Oct 7 13:34:57 2023 +0000
Updated site from master (aaaf48174b244d7d54ef9b8b0b6547a75c7482e8)
---
content/contributing/index.xml | 3 +--
content/contributing/releasing.html | 23 ++++++++++++++++-------
content/index.xml | 3 +--
content/sitemap.xml | 6 +++---
4 files changed, 21 insertions(+), 14 deletions(-)
diff --git a/content/contributing/index.xml b/content/contributing/index.xml
index 6a6e68c..afe872e 100644
--- a/content/contributing/index.xml
+++ b/content/contributing/index.xml
@@ -24,8 +24,7 @@ The following image visualizes the workflow Celix is
using:</description>
<guid>https://celix.apache.org/contributing/releasing.html</guid>
<description>Releasing Apache Celix Note: This information is only of
use to Apache Celix Release Managers!
Steps to follow:
-Create signing KEYS Create release branch Update release related files Compile
and test Create, sign and publish artifacts Run the vote Post the vote results
Vote Passed Create Git tag and merge to master Roll out release artifacts
Publish release documentation Update the website Announce the release
Interesting links:
-Apache Release Guide Apache Release Signing Apache RAT Apache OpenPGP HowTo
Create signing KEYS Each Release Manager must have his own signing
keys.</description>
+Create signing KEYS Create release branch Update release related files Compile
and test Create, sign and publish artifacts Run the vote Post the vote results
Vote Passed Create Git tag and merge to master Move release artifacts from
&ldquo;dev&rdquo; to &ldquo;release&rdquo; area Roll out
release artifacts Publish release documentation Update the website Announce the
release Interesting links:</description>
</item>
<item>
diff --git a/content/contributing/releasing.html
b/content/contributing/releasing.html
index 560d0fe..7140d5f 100644
--- a/content/contributing/releasing.html
+++ b/content/contributing/releasing.html
@@ -138,6 +138,7 @@
<li><a href="#vote-passed">Vote Passed</a>
<ul>
<li><a href="#create-git-tag-and-merge-to-master">Create Git tag and
merge to master</a></li>
+ <li><a href="#move-release-artifacts-from-dev-to-release-area">Move
release artifacts from “dev” to “release” area</a></li>
<li><a href="#roll-out-release-artifacts">Roll out release
artifacts</a></li>
<li><a href="#publish-release-documentation">Publish release
documentation</a></li>
<li><a href="#update-the-website">Update the website</a></li>
@@ -320,8 +321,9 @@ of votes made, including whether a vote is binding or not.
For a successful vote
</span></span><span style="display:flex;"><span>+1 Name of Approvers (not
binding)
</span></span><span style="display:flex;"><span>...
</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>The released artifact will be
moved to the release area for mirroring. The
-</span></span><span style="display:flex;"><span>release branch will be merged
with master and a 2.1.0 tag will be created.
+</span></span><span style="display:flex;"><span>The released artifact will be
moved to the release area for mirroring.
+</span></span><span style="display:flex;"><span>The X.Y.Z tag will be created
on the release branch and
+</span></span><span style="display:flex;"><span>the release branch will be
merged with the master branch.
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>After the mirroring period the
news & downloads of the website will be
</span></span><span style="display:flex;"><span>updated and the release will
be announced.
@@ -342,7 +344,7 @@ A tag - named like rel/celix-X.Y.Z - needs to created and
the release branch nee
</span></span><span style="display:flex;"><span>$ git config --global
user.signingkey E43F742E
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span
style="color:#080;font-style:italic"># Create the tag</span>
-</span></span><span style="display:flex;"><span>$ git tag -s rel/celix-X.Y.Z
-m <span style="color:#b44">'Celix release X.Y.Z'</span>
+</span></span><span style="display:flex;"><span>$ git tag -s rel/celix-X.Y.Z
-m <span style="color:#b44">'Apache Celix Release X.Y.Z'</span>
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span><span
style="color:#080;font-style:italic"># Next thing to do is pushing the tag to
the remote</span>
</span></span><span style="display:flex;"><span>$ git push origin
rel/celix-X.Y.Z
@@ -350,7 +352,12 @@ A tag - named like rel/celix-X.Y.Z - needs to created and
the release branch nee
</span></span><span style="display:flex;"><span>$ git checkout master
</span></span><span style="display:flex;"><span>$ git merge release-X.Y.Z
</span></span><span style="display:flex;"><span>$ git push origin master
-</span></span></code></pre></div><h3 id="roll-out-release-artifacts">Roll out
release artifacts</h3>
+</span></span></code></pre></div><h3
id="move-release-artifacts-from-dev-to-release-area">Move release artifacts
from “dev” to “release” area</h3>
+<p>First remove the previous release from the “release” area.</p>
+<p>Then use the following svn command to move the release artifacts from
“dev” to “release”:</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-bash" data-lang="bash"><span style="display:flex;"><span>svn
move https://dist.apache.org/repos/dist/dev/celix/celix-X.Y.Z
https://dist.apache.org/repos/dist/release/celix/
+</span></span></code></pre></div><p>Note that a svn move ensures that the
voted released artifacts are moved as-is.</p>
+<h3 id="roll-out-release-artifacts">Roll out release artifacts</h3>
<p>When a release is moved from the “dev” area to
“release” area. The automated
svnpubsub will move the artifact to the correct server for mirroring.
Mirroring typically can take up to 24 hours.</p>
<p>Besides uploading the new release, the old release should be archived.
Since archiving is already automated,
@@ -394,16 +401,18 @@ substituted with the actual released version). This file
can be copied and updat
<div class="highlight"><pre tabindex="0"
style="background-color:#f8f8f8;-moz-tab-size:4;-o-tab-size:4;tab-size:4;"><code
class="language-text" data-lang="text"><span style="display:flex;"><span>To:
[email protected], [email protected]
</span></span><span style="display:flex;"><span>Subject: [ANNOUNCE] Apache
Celix X.Y.Z released
</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>The Apache Celix team is
pleased to announce the release of Celix X.Y.Z.
</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>Celix is an implementation of
the OSGi specification adapted to C. It will follow the API as close as
possible, but since the OSGi specification is written primarily for Java, there
will be differences. An important aspect of the implementation is
interoperability between Java and C. This interoperability is achieved by
porting and implementing the Remote Services specification in Celix.
+</span></span><span style="display:flex;"><span>The Apache Celix team is
pleased to announce the release of Apache Celix X.Y.Z.
+</span></span><span style="display:flex;"><span>
+</span></span><span style="display:flex;"><span>Apache Celix is an
implementation of the OSGi specification adapted to C and C++.
+</span></span><span style="display:flex;"><span>It is a framework to develop
(dynamic) modular software applications using component and service-oriented
programming.
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>This new release focuses on
.... {add additional information for this release}
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>The release is available here:
</span></span><span
style="display:flex;"><span>https://celix.apache.org/download.cgi
</span></span><span style="display:flex;"><span>
-</span></span><span style="display:flex;"><span>The full change log is
available here:
+</span></span><span style="display:flex;"><span>The full change log is
available here: {add link to CHANGES.md}
</span></span><span style="display:flex;"><span>
</span></span><span style="display:flex;"><span>We welcome your help and
feedback. For more information on how to report problems, and to get involved,
visit the project website at https://celix.apache.org/
</span></span><span style="display:flex;"><span>
diff --git a/content/index.xml b/content/index.xml
index 9a4d9b0..a8e95d1 100644
--- a/content/index.xml
+++ b/content/index.xml
@@ -1588,8 +1588,7 @@ for every char device services found - a
&ldquo;word&rdquo; device servi
<guid>https://celix.apache.org/contributing/releasing.html</guid>
<description>Releasing Apache Celix Note: This information is only of
use to Apache Celix Release Managers!
Steps to follow:
-Create signing KEYS Create release branch Update release related files Compile
and test Create, sign and publish artifacts Run the vote Post the vote results
Vote Passed Create Git tag and merge to master Roll out release artifacts
Publish release documentation Update the website Announce the release
Interesting links:
-Apache Release Guide Apache Release Signing Apache RAT Apache OpenPGP HowTo
Create signing KEYS Each Release Manager must have his own signing
keys.</description>
+Create signing KEYS Create release branch Update release related files Compile
and test Create, sign and publish artifacts Run the vote Post the vote results
Vote Passed Create Git tag and merge to master Move release artifacts from
&ldquo;dev&rdquo; to &ldquo;release&rdquo; area Roll out
release artifacts Publish release documentation Update the website Announce the
release Interesting links:</description>
</item>
<item>
diff --git a/content/sitemap.xml b/content/sitemap.xml
index 879cd6b..662098e 100644
--- a/content/sitemap.xml
+++ b/content/sitemap.xml
@@ -3,7 +3,7 @@
xmlns:xhtml="http://www.w3.org/1999/xhtml";>
<url>
<loc>https://celix.apache.org/</loc>
- <lastmod>2023-10-07T13:55:07+02:00</lastmod>
+ <lastmod>2023-10-07T15:33:56+02:00</lastmod>
</url><url>
<loc>https://celix.apache.org/docs/2.3.0/celix/documents/bundles.html</loc>
<lastmod>2022-07-17T19:34:47+02:00</lastmod>
@@ -156,7 +156,7 @@
<lastmod>2022-07-14T18:57:22+02:00</lastmod>
</url><url>
<loc>https://celix.apache.org/contributing.html</loc>
- <lastmod>2023-09-19T22:09:16+02:00</lastmod>
+ <lastmod>2023-10-07T15:33:56+02:00</lastmod>
</url><url>
<loc>https://celix.apache.org/docs/2.1.0/celix/documents/getting_started/creating_a_simple_bundle.html</loc>
<lastmod>2020-02-03T15:43:09+01:00</lastmod>
@@ -447,7 +447,7 @@
<lastmod>2022-07-14T18:57:22+02:00</lastmod>
</url><url>
<loc>https://celix.apache.org/contributing/releasing.html</loc>
- <lastmod>2023-09-19T22:09:16+02:00</lastmod>
+ <lastmod>2023-10-07T15:33:56+02:00</lastmod>
</url><url>
<loc>https://celix.apache.org/docs/2.1.0/celix/remote_services/remote_service_admin/README.html</loc>
<lastmod>2020-02-03T15:43:09+01:00</lastmod>
