You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@karaf.apache.org by jg...@apache.org on 2013/03/04 05:21:31 UTC
svn commit: r1452182 - in /karaf/site/trunk/src/main/webapp: index.page
index/developers/release-guide.page
Author: jgoodyear
Date: Mon Mar 4 04:21:31 2013
New Revision: 1452182
URL: http://svn.apache.org/r1452182
Log:
[KARAF-1934] Release Apache Karaf 2.3.1
Modified:
karaf/site/trunk/src/main/webapp/index.page
karaf/site/trunk/src/main/webapp/index/developers/release-guide.page
Modified: karaf/site/trunk/src/main/webapp/index.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index.page?rev=1452182&r1=1452181&r2=1452182&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index.page (original)
+++ karaf/site/trunk/src/main/webapp/index.page Mon Mar 4 04:21:31 2013
@@ -60,7 +60,7 @@ new TWTR.Widget({
h2. News
-{incluse:news-2013-03-03}
+{include:news-2013-03-03}
{include:news-2013-02-17}
{include:news-2012-12-21}
{include:news-2012-12-06}
Modified: karaf/site/trunk/src/main/webapp/index/developers/release-guide.page
URL: http://svn.apache.org/viewvc/karaf/site/trunk/src/main/webapp/index/developers/release-guide.page?rev=1452182&r1=1452181&r2=1452182&view=diff
==============================================================================
--- karaf/site/trunk/src/main/webapp/index/developers/release-guide.page (original)
+++ karaf/site/trunk/src/main/webapp/index/developers/release-guide.page Mon Mar 4 04:21:31 2013
@@ -14,6 +14,7 @@ h3. Required tools, practices and resour
* Each and every release must be [SIGNED|http://www.apache.org/dev/release-signing.html]
* Your public key should also be cross-signed by other Apache committers (not required, but suggested)
* Make sure you have all Apache servers defined in your [settings.xml|http://maven.apache.org/developers/committer-settings.html]
+* Subversion client 1.7.8 or above.
h3. Versioning
@@ -164,6 +165,7 @@ cd manual ; mvn scalate:deploy
** commit the changes
** ?? should we do that in a branch and merge it later to trunk when the release is published, still need to be discussed related to how / if we maintain branches for the website ??
** ?? maybe include a pointer to the website trunk or branch in the vote email so that people can check the future website / release notes ??
+** Website update on site project, execute mvn clean install scm-publish:publish-scm -Dusername= -Dpassword=
h3. Starting the vote