Author: buildbot
Date: Tue Mar 3 14:27:09 2020
New Revision: 1057317
Log:
Staging update by buildbot for felix
Removed:
websites/staging/felix/trunk/content/documentation/development/svn-repository-structure.html
Modified:
websites/staging/felix/trunk/content/ (props changed)
websites/staging/felix/trunk/content/documentation/development.html
websites/staging/felix/trunk/content/documentation/development/committers.html
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
websites/staging/felix/trunk/content/sitemap.html
Propchange: websites/staging/felix/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue Mar 3 14:27:09 2020
@@ -1 +1 @@
-1874724
+1874727
Modified: websites/staging/felix/trunk/content/documentation/development.html
==============================================================================
--- websites/staging/felix/trunk/content/documentation/development.html
(original)
+++ websites/staging/felix/trunk/content/documentation/development.html Tue Mar
3 14:27:09 2020
@@ -104,7 +104,6 @@ h2:hover > .headerlink, h3:hover > .head
<li><a
href="/documentation/development/provisional-osgi-api-policy.html">Provisional
OSGi API Policy</a></li>
<li><a href="/documentation/development/release-management-nexus.html">Release
Management</a></li>
<li><a href="/documentation/development/source-code.html">Source Code</a></li>
-<li><a href="/documentation/development/svn-repository-structure.html">SVN
repository structure</a></li>
<li><a
href="/documentation/development/using-the-osgi-compliance-tests.html">Using
the OSGi Compliance Tests</a></li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
Modified:
websites/staging/felix/trunk/content/documentation/development/committers.html
==============================================================================
---
websites/staging/felix/trunk/content/documentation/development/committers.html
(original)
+++
websites/staging/felix/trunk/content/documentation/development/committers.html
Tue Mar 3 14:27:09 2020
@@ -94,10 +94,10 @@ h2:hover > .headerlink, h3:hover > .head
Well there are a number of things that can be done. </p>
<ul>
<li>First of all, subscribe to the Felix dev mailing list and participate
there.</li>
-<li>Add patches to issues in the issue management tool.</li>
+<li>Create a pull request and link it to an issue in the issue management
tool.</li>
</ul>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1777624 by sseifert on Fri, 6 Jan 2017 15:00:09 +0000
+ Rev. 1874727 by cziegeler on Tue, 3 Mar 2020 14:26:27 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache
Felix project
Modified:
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
==============================================================================
---
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
(original)
+++
websites/staging/felix/trunk/content/documentation/development/release-management-nexus.html
Tue Mar 3 14:27:09 2020
@@ -88,7 +88,7 @@ h2:hover > .headerlink, h3:hover > .head
visibility: hidden;
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
-<p><em>This is the new release process for Apache Felix, based on the updated
Maven <a
href="http://maven.apache.org/developers/release/releasing.html";>process</a></em></p>
+<p>*This is the release process for Apache Felix, based on Apache Maven <a
href="https://maven.apache.org/developers/release/releasing.html";>process</a></p>
<h2 id="basics">Basics<a class="headerlink" href="#basics" title="Permanent
link">¶</a></h2>
<p>Apache Felix artifacts are distributed in two channels: The Maven
Repository and the Apache
distribution channels.</p>
@@ -99,7 +99,7 @@ distribution channels.</p>
<li><a href="#starting-the-vote">Call for vote</a></li>
<li><a href="#promoting-the-release">Publish the release candidate</a>:<ul>
<li>Publish the staged artifacts from Nexus Staging</li>
-<li><code>svn add</code> the artifacts to Subversion repository and <code>svn
rm</code> the artifacts from the previous release</li>
+<li><code>svn add</code> the artifacts to the <code>dist</code> Subversion
repository and <code>svn rm</code> the artifacts from the previous release</li>
</ul>
</li>
<li><a href="#create-an-announcement">Announce the release</a></li>
@@ -114,13 +114,13 @@ In this case please ask a member of the
<h2 id="prerequisites">Prerequisites<a class="headerlink"
href="#prerequisites" title="Permanent link">¶</a></h2>
<p>To prepare or perform a release you <em>MUST BE</em> at least an Apache
Felix Committer.</p>
<ul>
-<li>each and every release must be <a
href="http://www.apache.org/dev/release-signing.html";>SIGNED</a>; your public
key should be added to [http://www.apache.org/dist/felix/KEYS] (see
<em>Appendix A</em>)</li>
+<li>each and every release must be <a
href="https://www.apache.org/dev/release-signing.html";>SIGNED</a>; your public
key should be added to [https://www.apache.org/dist/felix/KEYS] (see
<em>Appendix A</em>)</li>
<li>your public key should also be cross-signed by other Apache committers
(not required, but suggested)</li>
<li>when preparing the release on Mac OS X, make sure you read <em>Appendix
B</em> before continuing</li>
-<li>make sure you have all Apache servers defined in your <a
href="http://maven.apache.org/developers/committer-settings.html";>settings.xml</a></li>
-<li>use Maven 2.0.x (or 2.2.x), as Maven 2.1.x is known to produce wrong gpg
pom signatures (<a
href="http://jira.codehaus.org/browse/MGPG-14";>MGPG-14</a>)</li>
+<li>make sure you have all Apache servers defined in your <a
href="https://maven.apache.org/developers/committer-settings.html";>settings.xml</a></li>
+<li>use Maven 3.5.0 (or higher) </li>
</ul>
-<p><em>Note</em>: Listing the Apache servers in the <code>settings.xml</code>
file also requires adding the password to that file. Starting with Maven 2.1
this password may be encrypted and needs not be give in plaintext. Please refer
to <a href="http://maven.apache.org/guides/mini/guide-encryption.html";>Password
Encryption</a> for more information.</p>
+<p><em>Note</em>: Listing the Apache servers in the <code>settings.xml</code>
file also requires adding the password to that file. Starting with Maven 2.1
this password may be encrypted and needs not be give in plaintext. Please refer
to <a
href="https://maven.apache.org/guides/mini/guide-encryption.html";>Password
Encryption</a> for more information.</p>
<p>In the past we staged release candidates on our local machines using a
semi-manual process. Now that we inherit from the Apache parent POM version 5,
a repository manager will automatically handle staging for you. This means you
now only need to specify your GPG passphrase in the release profile of your
<code>$\{user.home\}/.m2/settings.xml</code>:</p>
<div class="codehilite"><pre><span class="nt"><settings></span>
...
@@ -141,7 +141,7 @@ In this case please ask a member of the
<div class="codehilite"><pre><span class="nt"><parent></span>
<span class="nt"><groupId></span>org.apache.felix<span
class="nt"></groupId></span>
<span class="nt"><artifactId></span>felix-parent<span
class="nt"></artifactId></span>
- <span class="nt"><version></span>1.2.0<span
class="nt"></version></span>
+ <span class="nt"><version></span>6<span
class="nt"></version></span>
<span class="nt"><relativePath></span>../pom/pom.xml<span
class="nt"></relativePath></span>
<span class="nt"></parent></span>
</pre></div>
@@ -166,14 +166,14 @@ the released version.
[INFO] Retrieving previous build number from apache.snapshots.https<br />
...</code></div><ul>
<li>if you experience an error during deployment like a HTTP 401 check your
settings for the required server entries as outlined in the
<em>Prerequisites</em></li>
-<li>be sure that the generated artifacts respect the Apache release <a
href="http://www.apache.org/dev/release.html";>rules</a>: NOTICE and LICENSE
files should be present in the META-INF directory within the jar. For -sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3
which is broken. The recommended version at this time is 2.0.4</li>
+<li>be sure that the generated artifacts respect the Apache release <a
href="https://www.apache.org/dev/release.html";>rules</a>: NOTICE and LICENSE
files should be present in the META-INF directory within the jar. For -sources
artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3
which is broken. The recommended version at this time is 2.0.4</li>
<li>you should verify the deployment under the <a
href="https://repository.apache.org/content/groups/snapshots/org/apache/felix";>snapshot</a>
repository on Apache</li>
</ul>
</li>
<li>Prepare the release
<div class="codehilite"><code>$ mvn release:clean <br />
$ mvn release:prepare</code></div><ul>
-<li>preparing the release will create the new tag in SVN, automatically
checking in on your behalf</li>
+<li>preparing the release will create the new tag in git, automatically
checking in on your behalf</li>
</ul>
</li>
<li>Stage the release for a vote
@@ -209,7 +209,7 @@ Staging repository:
https://repository.apache.org/content/repositories/orgapachefelix-[YOUR
REPOSITORY ID]/
You can use this UNIX script to download the release and verify the signatures:
-http://svn.apache.org/repos/asf/felix/trunk/check_staged_release.sh
+https://github.com/apache/felix-dev/blob/master/check_staged_release.sh
Usage:
sh check_staged_release.sh [YOUR REPOSITORY ID] /tmp/felix-staging
@@ -223,10 +223,10 @@ This vote will be open for 72 hours.
</pre></div>
-<p>To get the JIRA release notes link, browse to the FELIX <a
href="http://issues.apache.org/jira/browse/FELIX";>JIRA</a> page, select
[Release
Notes|http://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310100]
and choose the relevant sub-project release and format (HTML)</p>
-<p>To get the list of issues left in JIRA, select the <a
href="http://issues.apache.org/jira/browse/FELIX?report=com.atlassian.jira.plugin.system.project:openissues-panel";>Open
Issues</a> tab on the main FELIX page, and select the relevant sub-project.</p>
+<p>To get the JIRA release notes link, browse to the FELIX <a
href="https://issues.apache.org/jira/browse/FELIX";>JIRA</a> page, select
[Release
Notes|https://issues.apache.org/jira/secure/ConfigureReleaseNote.jspa?projectId=12310100]
and choose the relevant sub-project release and format (HTML)</p>
+<p>To get the list of issues left in JIRA, select the <a
href="https://issues.apache.org/jira/browse/FELIX?report=com.atlassian.jira.plugin.system.project:openissues-panel";>Open
Issues</a> tab on the main FELIX page, and select the relevant sub-project.</p>
<h2 id="wait-for-the-results">Wait for the Results<a class="headerlink"
href="#wait-for-the-results" title="Permanent link">¶</a></h2>
-<p>From <a href="http://www.apache.org/foundation/voting.html";>Votes on
Package Releases</a>:</p>
+<p>From <a href="https://www.apache.org/foundation/voting.html";>Votes on
Package Releases</a>:</p>
<blockquote>
<p>Votes on whether a package is ready to be released follow a format similar
to majority approval -- except that the decision is officially determined
solely by whether at least three +1 votes were registered. Releases may not be
vetoed. Generally the community will table the vote to release if anyone
identifies serious problems, but in most cases the ultimate decision, once
three or more positive votes have been garnered, lies with the individual
serving as release manager. The specifics of the process may vary from project
to project, but the 'minimum of three +1 votes' rule is universal.</p>
</blockquote>
@@ -417,7 +417,7 @@ svn: MKACTIVITY of '/repos/asf/!svn/
<p>This is due to a bug in Subversion on the Mac, as described by Brett Porter
in his
[blog|http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/].
He proposes putting an "svn" script at the head of your path to fix the
issue.</p>
<div class="timestamp" style="margin-top: 30px; font-size: 80%;
text-align: right;">
- Rev. 1819013 by sseifert on Fri, 22 Dec 2017 09:03:09 +0000
+ Rev. 1874727 by cziegeler on Tue, 3 Mar 2020 14:26:27 +0000
</div>
<div class="trademarkFooter">
Apache Felix, Felix, Apache, the Apache feather logo, and the Apache
Felix project
Modified: websites/staging/felix/trunk/content/sitemap.html
==============================================================================
--- websites/staging/felix/trunk/content/sitemap.html (original)
+++ websites/staging/felix/trunk/content/sitemap.html Tue Mar 3 14:27:09 2020
@@ -113,7 +113,6 @@ h2:hover > .headerlink, h3:hover > .head
<li><a
href="/documentation/development/provisional-osgi-api-policy.html">Provisional
OSGi API Policy</a></li>
<li><a href="/documentation/development/release-management-nexus.html">Release
Management</a></li>
<li><a href="/documentation/development/source-code.html">Source Code</a></li>
-<li><a href="/documentation/development/svn-repository-structure.html">SVN
repository structure</a></li>
<li><a
href="/documentation/development/using-the-osgi-compliance-tests.html">Using
the OSGi Compliance Tests</a></li>
</ul>
</li>
