DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
...
| Code Block |
|---|
<settings>
...
<profiles>
<profile>
<id>release</id>
<properties>
<gpg.passphrase> <!-- YOUR KEY PASSPHRASE --> </gpg.passphrase>
</properties>
</profile>
</profiles>
...
<servers>
<!-- To publish a snapshot of some part of Maven -->
<server>
<id>apache.snapshots.https</id>
<username> <!-- YOUR APACHE SVN USERNAME --> </username>
<password> <!-- YOUR APACHE SVN PASSWORD --> </password>
</server>
<!-- To stage a release of some part of Maven -->
<server>
<id>apache.releases.https</id>
<username> <!-- YOUR APACHE SVN USERNAME --> </username>
<password> <!-- YOUR APACHE SVN PASSWORD --> </password>
</server>
...
</servers>
</settings>
|
Community awareness message(s).
In the lead up towards a release candidate the user base should be given some notification.
In the case of dot zero release a new maintenance branch may be created with trunk continuing new development. The maintenance branch may be used for stabilization of the code base before a release candidate is cut. A notification message to the dev & user lists may be warranted.
| Code Block |
|---|
To: "Karaf Developers List" <dev@karaf.apache.org>
Subject: [NOTICE] Karaf trunk branched to create X.Y.0 maintenance branch.
Hi,
We've just branched off X.Y.0 from trunk and started to stabilize it; latest artifacts are
available via apache-snapshot repo... simply add the following repo to your pom,
change the version to and provide us with feedback.
<<insert short description of the reason for branching here>>
Thanks,
-The Karaf team
|
A few weeks later the following message would be sent:
| Code Block |
|---|
To: "Karaf Developers List" <dev@karaf.apache.org>
Subject: [UPDATE] Karaf X.Y.0 release branch status.
Hi,
Thanks for all your feedback; we've fixed XX bugs/problems on the release branch
and will start a release about next week; Thanks again for all your contributions.
-The Karaf Team
|
Staging the Release Candidate
...