You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by bu...@apache.org on 2012/12/12 10:17:17 UTC
svn commit: r841833 [21/28] - in /websites/staging/sling/trunk/content: ./
site/ site/46-line-blog.data/ site/authentication.data/
site/documentation.data/ site/first-steps.data/
site/getting-and-building-sling.data/ site/how-to-manage-events-in-sling....
Added: websites/staging/sling/trunk/content/site/project-license.html
==============================================================================
--- websites/staging/sling/trunk/content/site/project-license.html (added)
+++ websites/staging/sling/trunk/content/site/project-license.html Wed Dec 12 09:16:44 2012
@@ -0,0 +1,272 @@
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<HTML>
+ <HEAD>
+ <TITLE>Apache Sling - Project License</TITLE>
+ <LINK rel="stylesheet" href="http://sling.apache.org/site/media.data/site.css" type="text/css" media="all">
+ <LINK rel="icon" href="http://sling.apache.org/site/media.data/favicon.ico">
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ </HEAD>
+ <BODY>
+ <DIV class="title">
+ <DIV class="logo">
+ <A href="http://sling.apache.org/site/index.html">
+ <IMG border="0" alt="Apache Sling" src="http://sling.apache.org/site/media.data/logo.png">
+ </A>
+ </DIV>
+ <DIV class="header">
+ <A href="http://www.apache.org/">
+ <IMG border="0" alt="Apache" src="http://sling.apache.org/site/media.data/apache.png">
+ </A>
+ </DIV>
+ </DIV>
+ <DIV class="menu">
+<P><B>Documentation</B><BR class="atl-forced-newline">
+<A href="getting-started.html" title="Getting Started">Getting Started</A><BR class="atl-forced-newline">
+<A href="the-sling-engine.html" title="The Sling Engine">The Sling Engine</A><BR class="atl-forced-newline">
+<A href="development.html" title="Development">Development</A><BR class="atl-forced-newline">
+<A href="bundles.html" title="Bundles">Bundles</A><BR class="atl-forced-newline">
+<A href="tutorials-how-tos.html" title="Tutorials & How-Tos">Tutorials & How-Tos</A><BR class="atl-forced-newline">
+<A href="configuration.html" title="Configuration">Configuration</A><BR class="atl-forced-newline">
+<A href="http://sling.apache.org/apidocs/sling6/index.html" class="external-link" rel="nofollow">API docs</A><BR class="atl-forced-newline">
+<A href="http://s.apache.org/sling.wiki" class="external-link" rel="nofollow">Wiki</A><BR class="atl-forced-newline">
+<A href="http://s.apache.org/sling.faq" class="external-link" rel="nofollow">FAQ</A><BR class="atl-forced-newline"></P>
+
+<P><B>Project info</B><BR class="atl-forced-newline">
+<A href="http://sling.apache.org/site/downloads.cgi" class="external-link" rel="nofollow">Downloads</A><BR class="atl-forced-newline">
+<A href="http://www.apache.org/licenses/" class="external-link" rel="nofollow">License</A><BR class="atl-forced-newline">
+<A href="contributing.html" title="Contributing">Contributing</A><BR class="atl-forced-newline">
+<A href="news.html" title="News">News</A><BR class="atl-forced-newline">
+<A href="links.html" title="Links">Links</A><BR class="atl-forced-newline">
+<A href="project-information.html" title="Project Information">Project Information</A><BR class="atl-forced-newline">
+<A href="https://issues.apache.org/jira/browse/SLING" class="external-link" rel="nofollow">Issue Tracker</A><BR class="atl-forced-newline">
+<A href="http://svn.apache.org/viewvc/sling/trunk" class="external-link" rel="nofollow">Browse Source Repository</A><BR class="atl-forced-newline">
+<A href="security.html" title="Security">Security</A><BR class="atl-forced-newline"></P>
+
+<P><B>Sponsorship</B><BR class="atl-forced-newline">
+<A href="http://www.apache.org/foundation/thanks.html" class="external-link" rel="nofollow">Thanks</A><BR class="atl-forced-newline">
+<A href="http://www.apache.org/foundation/sponsorship.html" class="external-link" rel="nofollow">Become a Sponsor</A><BR>
+<A href="http://www.apache.org/foundation/buy_stuff.html" class="external-link" rel="nofollow">Buy Stuff</A></P>
+
+
+ <IFRAME src="http://www.apache.org/ads/button.html" style="border-width:0; float: left" frameborder="0" scrolling="no" width="135" height="135"></IFRAME>
+ <P style="height: 135px"></P>
+ </DIV>
+ <DIV class="main">
+ <DIV class="breadcrump" style="font-size: 80%;">
+<A href="apache-sling.html" title="Apache Sling Website">Apache Sling Website</A> > <A href="apache-sling.html" title="Apache Sling">Apache Sling</A> > <A href="project-information.html" title="Project Information">Project Information</A> > <A href="" title="Project License">Project License</A>
+ </DIV>
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE> Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
+
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+ 1. Definitions.
+
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+</PRE>
+</DIV></DIV>
+ <DIV class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
+Last modified by fmeschbe on 2008-02-11 05:49:55.0
+ </DIV>
+ <DIV class="trademarkFooter">
+Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
+ </DIV>
+ </DIV>
+ </BODY>
+</HTML>
+
Added: websites/staging/sling/trunk/content/site/project-team.html
==============================================================================
--- websites/staging/sling/trunk/content/site/project-team.html (added)
+++ websites/staging/sling/trunk/content/site/project-team.html Wed Dec 12 09:16:44 2012
@@ -0,0 +1,264 @@
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<HTML>
+ <HEAD>
+ <TITLE>Apache Sling - Project Team</TITLE>
+ <LINK rel="stylesheet" href="http://sling.apache.org/site/media.data/site.css" type="text/css" media="all">
+ <LINK rel="icon" href="http://sling.apache.org/site/media.data/favicon.ico">
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ </HEAD>
+ <BODY>
+ <DIV class="title">
+ <DIV class="logo">
+ <A href="http://sling.apache.org/site/index.html">
+ <IMG border="0" alt="Apache Sling" src="http://sling.apache.org/site/media.data/logo.png">
+ </A>
+ </DIV>
+ <DIV class="header">
+ <A href="http://www.apache.org/">
+ <IMG border="0" alt="Apache" src="http://sling.apache.org/site/media.data/apache.png">
+ </A>
+ </DIV>
+ </DIV>
+ <DIV class="menu">
+<P><B>Documentation</B><BR class="atl-forced-newline">
+<A href="getting-started.html" title="Getting Started">Getting Started</A><BR class="atl-forced-newline">
+<A href="the-sling-engine.html" title="The Sling Engine">The Sling Engine</A><BR class="atl-forced-newline">
+<A href="development.html" title="Development">Development</A><BR class="atl-forced-newline">
+<A href="bundles.html" title="Bundles">Bundles</A><BR class="atl-forced-newline">
+<A href="tutorials-how-tos.html" title="Tutorials & How-Tos">Tutorials & How-Tos</A><BR class="atl-forced-newline">
+<A href="configuration.html" title="Configuration">Configuration</A><BR class="atl-forced-newline">
+<A href="http://sling.apache.org/apidocs/sling6/index.html" class="external-link" rel="nofollow">API docs</A><BR class="atl-forced-newline">
+<A href="http://s.apache.org/sling.wiki" class="external-link" rel="nofollow">Wiki</A><BR class="atl-forced-newline">
+<A href="http://s.apache.org/sling.faq" class="external-link" rel="nofollow">FAQ</A><BR class="atl-forced-newline"></P>
+
+<P><B>Project info</B><BR class="atl-forced-newline">
+<A href="http://sling.apache.org/site/downloads.cgi" class="external-link" rel="nofollow">Downloads</A><BR class="atl-forced-newline">
+<A href="http://www.apache.org/licenses/" class="external-link" rel="nofollow">License</A><BR class="atl-forced-newline">
+<A href="contributing.html" title="Contributing">Contributing</A><BR class="atl-forced-newline">
+<A href="news.html" title="News">News</A><BR class="atl-forced-newline">
+<A href="links.html" title="Links">Links</A><BR class="atl-forced-newline">
+<A href="project-information.html" title="Project Information">Project Information</A><BR class="atl-forced-newline">
+<A href="https://issues.apache.org/jira/browse/SLING" class="external-link" rel="nofollow">Issue Tracker</A><BR class="atl-forced-newline">
+<A href="http://svn.apache.org/viewvc/sling/trunk" class="external-link" rel="nofollow">Browse Source Repository</A><BR class="atl-forced-newline">
+<A href="security.html" title="Security">Security</A><BR class="atl-forced-newline"></P>
+
+<P><B>Sponsorship</B><BR class="atl-forced-newline">
+<A href="http://www.apache.org/foundation/thanks.html" class="external-link" rel="nofollow">Thanks</A><BR class="atl-forced-newline">
+<A href="http://www.apache.org/foundation/sponsorship.html" class="external-link" rel="nofollow">Become a Sponsor</A><BR>
+<A href="http://www.apache.org/foundation/buy_stuff.html" class="external-link" rel="nofollow">Buy Stuff</A></P>
+
+
+ <IFRAME src="http://www.apache.org/ads/button.html" style="border-width:0; float: left" frameborder="0" scrolling="no" width="135" height="135"></IFRAME>
+ <P style="height: 135px"></P>
+ </DIV>
+ <DIV class="main">
+ <DIV class="breadcrump" style="font-size: 80%;">
+<A href="apache-sling.html" title="Apache Sling Website">Apache Sling Website</A> > <A href="apache-sling.html" title="Apache Sling">Apache Sling</A> > <A href="project-information.html" title="Project Information">Project Information</A> > <A href="" title="Project Team">Project Team</A>
+ </DIV>
+<H1><A name="ProjectTeam-TheProjectTeam"></A>The Project Team</H1>
+
+<P>A successful project requires many people to play many roles. Some members write code or documentation, while others are valuable as testers, submitting patches and suggestions.</P>
+
+<P>The team is comprised of Committers and Contributors. Committers have direct access to the source of a project and actively evolve the code-base. Contributors improve the project through submission of patches and suggestions to the Members. The number of Contributors to the project is unbounded. Get involved today. All contributions to the project are greatly appreciated.</P>
+
+<H2><A name="ProjectTeam-CommittersandPMCmembers"></A>Committers and PMC members</H2>
+
+<P>The following is a list of developers with commit privileges that have directly contributed to the project in one way or another.</P>
+
+<DIV class="table-wrap">
+<TABLE class="confluenceTable"><TBODY>
+<TR>
+<TH class="confluenceTh"> Id </TH>
+<TH class="confluenceTh"> Name </TH>
+<TH class="confluenceTh"> Organization </TH>
+<TH class="confluenceTh"> Roles </TH>
+<TH class="confluenceTh"> Time Zone </TH>
+</TR>
+<TR>
+<TD class="confluenceTd"> aheimoz </TD>
+<TD class="confluenceTd"> Alison Heimoz </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Technical Writer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> apopescu <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Alexandru Popescu </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> asanso </TD>
+<TD class="confluenceTd"> Antonio Sanso </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> bdelacretaz <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Bertrand Delacretaz </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Clemens Wyss </TD>
+<TD class="confluenceTd"> MySign AG </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> clombart <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Christophe Lombart </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> cziegeler <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Carsten Ziegeler </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Chair, Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> fmeschbe <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Felix Meschberger </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> enorman </TD>
+<TD class="confluenceTd"> Eric Norman </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> gianugo <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Gianugo Rabellino </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> jckautzmann </TD>
+<TD class="confluenceTd"> Jean-Christophe Kautzmann </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> justin <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Justin Edelson </TD>
+<TD class="confluenceTd"> Adobe </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> hannonpi <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Padraic Hannon </TD>
+<TD class="confluenceTd"> Edmunds Inc. </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> ieb <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Ian Boston </TD>
+<TD class="confluenceTd"> University of Cambridge </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> juanjo <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Juan José Vázquez Delgado </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> mykee <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Mike Müller </TD>
+<TD class="confluenceTd"> MySign AG </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> pauls <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Karl Pauls </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> thecarlhall </TD>
+<TD class="confluenceTd"> Carl Hall </TD>
+<TD class="confluenceTd"> Hallway Technologies </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> -5 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> vramdal <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> </TD>
+<TD class="confluenceTd"> Vidar Ramdal </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Java Developer </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+</TBODY></TABLE>
+</DIV>
+
+
+<P>Committers marked with an asterisk <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/star_yellow.gif" height="16" width="16" align="absmiddle" alt="" border="0"> are also members of the Sling Project Management Commitee (<A href="http://www.apache.org/dev/pmc.html" class="external-link" rel="nofollow">PMC</A>) as defined in <A href="apache-sling-community-roles-and-processes.html" title="Apache Sling Community Roles and Processes">Apache Sling Community Roles and Processes</A></P>
+
+
+<H2><A name="ProjectTeam-EmeritusCommittersandPMCmembers"></A>Emeritus Committers and PMC members</H2>
+
+<P>The following list of former committers and/or PMC members have chosen to go emeritus. We are still thankful for their help and guidance during earlier phases of the Sling project.</P>
+
+<DIV class="table-wrap">
+<TABLE class="confluenceTable"><TBODY>
+<TR>
+<TH class="confluenceTh"> Id </TH>
+<TH class="confluenceTh"> Name </TH>
+<TH class="confluenceTh"> Organization </TH>
+<TH class="confluenceTh"> Roles </TH>
+<TH class="confluenceTh"> Time Zone </TH>
+</TR>
+<TR>
+<TD class="confluenceTd"> farra </TD>
+<TD class="confluenceTd"> <B>J Aaron Farr</B> </TD>
+<TD class="confluenceTd"> </TD>
+<TD class="confluenceTd"> Mentor </TD>
+<TD class="confluenceTd"> </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> jukka </TD>
+<TD class="confluenceTd"> <B>Jukka Zitting</B> </TD>
+<TD class="confluenceTd"> Day Software </TD>
+<TD class="confluenceTd"> Champion, Mentor </TD>
+<TD class="confluenceTd"> +1 </TD>
+</TR>
+</TBODY></TABLE>
+</DIV>
+
+
+<P>Committers with their names printed in bold face have also been members of the PMC (or PPMC during Sling incubation) as defined in <A href="apache-sling-community-roles-and-processes.html" title="Apache Sling Community Roles and Processes">Apache Sling Community Roles and Processes</A></P>
+
+
+<H2><A name="ProjectTeam-Contributors"></A>Contributors</H2>
+
+<P>There are no contributors listed for this project.</P>
+ <DIV class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
+Last modified by aheimoz on Wed Sep 26 08:30:12 EDT 2012
+ </DIV>
+ <DIV class="trademarkFooter">
+Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
+ </DIV>
+ </DIV>
+ </BODY>
+</HTML>
+
Added: websites/staging/sling/trunk/content/site/provisioning-and-startup.html
==============================================================================
--- websites/staging/sling/trunk/content/site/provisioning-and-startup.html (added)
+++ websites/staging/sling/trunk/content/site/provisioning-and-startup.html Wed Dec 12 09:16:44 2012
@@ -0,0 +1,199 @@
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<HTML>
+ <HEAD>
+ <TITLE>Apache Sling - Provisioning and Startup</TITLE>
+ <LINK rel="stylesheet" href="http://incubator.apache.org/sling/site/media.data/site.css" type="text/css" media="all">
+ <LINK rel="icon" href="http://incubator.apache.org/sling/site/media.data/favicon.ico">
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ </HEAD>
+ <BODY>
+ <DIV class="title">
+ <DIV class="logo">
+ <A href="http://incubator.apache.org/sling/site/index.html">
+ <IMG border="0" alt="Apache Sling" src="http://incubator.apache.org/sling/site/media.data/logo.png">
+ </A>
+ </DIV>
+ <DIV class="header">
+ <A href="http://incubator.apache.org/">
+ <IMG border="0" alt="Apache Incubator" src="http://incubator.apache.org/images/apache-incubator-logo.png">
+ </A>
+ </DIV>
+ </DIV>
+ <DIV class="menu">
+ <P style="display: none"></P>
+
+<UL>
+ <LI><A href="documentation.html" title="Documentation">Documentation</A></LI>
+ <LI><A href="advanced-topics.html" title="Advanced Topics">Advanced Topics</A></LI>
+ <LI><A href="development.html" title="Development">Development</A></LI>
+ <LI><SPAN class="nobr"><A href="http://incubator.apache.org/sling/site/downloads.cgi" title="Visit page outside Confluence" rel="nofollow">Downloads<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><A href="contributing.html" title="Contributing">Contributing</A></LI>
+ <LI><A href="links.html" title="Links">Links</A></LI>
+ <LI><SPAN class="nobr"><A href="http://cwiki.apache.org/SLING/faq.html" title="Visit page outside Confluence" rel="nofollow">FAQ<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><SPAN class="nobr"><A href="http://cwiki.apache.org/SLING/" title="Visit page outside Confluence" rel="nofollow">Wiki<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><A href="project-information.html" title="Project Information">Project Information</A></LI>
+ <LI><SPAN class="nobr"><A href="http://incubator.apache.org/sling/apidocs/sling5/index.html" title="Visit page outside Confluence" rel="nofollow">Sling 5 API<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><SPAN class="nobr"><A href="http://www.apache.org/foundation/thanks.html" title="Visit page outside Confluence" rel="nofollow">Sponsors<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><SPAN class="nobr"><A href="http://www.apache.org/foundation/sponsorship.html" title="Visit page outside Confluence" rel="nofollow">Sponsorship<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN>
+
+<IFRAME src="http://www.apache.org/ads/button.html" style="border-width:0; float: left" frameborder="0" scrolling="no" width="135" height="135"></IFRAME>
+<P style="height: 100px"></P>
+</LI>
+</UL>
+ </DIV>
+ <DIV class="main">
+ <DIV class="breadcrump" style="font-size: 80%;">
+<A href="apache-sling.html" title="Apache Sling Website">Apache Sling Website</A> > <A href="apache-sling.html" title="Apache Sling">Apache Sling</A> > <A href="advanced-topics.html" title="Advanced Topics">Advanced Topics</A> > <A href="" title="Provisioning and Startup">Provisioning and Startup</A>
+ </DIV>
+<H1><A name="ProvisioningandStartup-InitialProvisioningandStartup"></A>Initial Provisioning and Startup</H1>
+
+<TABLE cellpadding="5" width="85%" cellspacing="8px" class="noteMacro" border="0" align="center"><COLGROUP><COL width="24"><COL></COLGROUP><TR><TD valign="top"><IMG src="http://cwiki.apache.org/confluence/images/icons/emoticons/warning.gif" width="16" height="16" align="absmiddle" alt="" border="0"></TD><TD>
+<P>The information presented on this page is currently (13-Apr-2009) not up to date. We are in the process of updating the site and will also fix this page.</P></TD></TR></TABLE>
+
+<H2><A name="ProvisioningandStartup-WegotaLaunch"></A>We got a Launch</H2>
+
+<P>The most complicated tasks getting Sling or any Sling application up and running is launching the framework and providing the initial installation. To simplify these tasks, great efforts have been taken. The result is a Standalone Java Application - the Sling App - and a Web Application - the Sling Servlet - with embedded libraries and a core set of bundles and a mechanism to provide initial configuration and installation. The following description applies to both the standalone application and the web application.</P>
+
+<P>When Sling is first started the following steps are executed:</P>
+
+<UL>
+ <LI>The initial configuration is loaded as described <A href="configuration.html#Configuration-InitialConfiguration" title="Initial_Configuration on Configuration">here</A>.</LI>
+ <LI>The list of bundles embedded in the application is set to the <TT>felix.autostart.1</TT> property. This will automatically install and start these bundles in start level 1. Currently this list is hard coded and consists of the following bundles:</LI>
+ <LI><TT>org.apache.sling.sling-log</TT> - The OSGi Log Service implementation of Project Sling also exporting logging APIs</LI>
+ <LI><TT>org.apache.sling.sling-assembly</TT> - Installation and Update Management support</LI>
+ <LI><TT>org.apache.felix.bundlerepository</TT> - Apache Felix implementation of the OSGi Bundle Repository specification.</LI>
+ <LI>The Apache Felix framework is launched and an URL handler for the <TT>context:</TT> scheme is registered to provide access to the contents of the Sling Web Application.</LI>
+ <LI>As soon as the Framework has been started, the <TT>com.day.sling.assembly</TT> bundle inspects the Framework properties available through the <TT>BundleContext.getProperty(String)</TT> method to install bundles from configured OSGi Bundle Repositories.</LI>
+</UL>
+
+
+
+
+<H2><A name="ProvisioningandStartup-InitialBundleInstallationbytheslingassemblyBundle"></A>Initial Bundle Installation by the sling-assembly Bundle</H2>
+
+<P>When the <EM>sling-assembly</EM> bundle is started it registers a <TT>FrameworkEventListener</TT> which justs listens for the <TT>FRAMEWORK_STARTED</TT> event. When this event comes in, the framework is up and running, the <EM>sling-assembly</EM> bundle will look at the Framework properties to see, whether any bundles need to be installed. This is done along the lines of the following pseudo code:</P>
+
+<DIV class="code"><DIV class="codeContent">
+<PRE class="code-java"><SPAN class="code-object">String</SPAN> startLevelList = bundleContext.getProperty( <SPAN class="code-quote">"sling.install.bundles"</SPAN> );
+<SPAN class="code-keyword">for</SPAN> ( <SPAN class="code-object">String</SPAN> startLevel: startLevelList ) {
+ <SPAN class="code-object">String</SPAN> bundleList = bundleContext.getProperty( <SPAN class="code-quote">"sling.install."</SPAN> + startLevel );
+ <SPAN class="code-keyword">for</SPAN> ( Bundle bundle: bundleList ) {
+ <SPAN class="code-keyword">if</SPAN> ( ! isInstalled( bundle ) ) {
+ install( bundle );
+ setStartLevel( bundle, startLevel );
+ }
+ }
+}
+
+<SPAN class="code-keyword">for</SPAN> ( each bundle installed ) {
+ start( bundle );
+}</PRE>
+</DIV></DIV>
+
+
+<H3><A name="ProvisioningandStartup-Example"></A>Example</H3>
+
+<P>Given the following properties</P>
+
+<DIV class="preformatted"><DIV class="preformattedContent">
+<PRE>sling.install.bundles = 1, 10, 20
+sling.install.1 = org.apache.sling.assemblies.osgi-compendium-assembly:0.1.0, \
+ org.apache.sling.assemblies.sling-console-web-assembly:0.1.0
+sling.install.10 = org.apache.sling.assemblies.sling-crx-server-assembly:[1,2)
+sling.install.20 = org.apache.sling.assemblies.sling-assembly$
+</PRE>
+</DIV></DIV>
+
+
+<P>These bundles will be installed:</P>
+
+<TABLE class="confluenceTable"><TBODY>
+<TR>
+<TH class="confluenceTh"> Bundle </TH>
+<TH class="confluenceTh"> Version </TH>
+<TH class="confluenceTh"> Start Level </TH>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>org.apache.sling.assemblies.osgi-compendium-assembly</TT> </TD>
+<TD class="confluenceTd"> >= 0.1.0 </TD>
+<TD class="confluenceTd"> 1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>org.apache.sling.assemblies.sling-console-web-assembly</TT> </TD>
+<TD class="confluenceTd"> >= 0.1.0 </TD>
+<TD class="confluenceTd"> 1 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>org.apache.sling.assemblies.sling-crx-server-assembly</TT> </TD>
+<TD class="confluenceTd"> Any Version with Major Version 1 </TD>
+<TD class="confluenceTd"> 10 </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>org.apache.sling.assemblies.sling-assembly</TT> </TD>
+<TD class="confluenceTd"> Any Version </TD>
+<TD class="confluenceTd"> 20 </TD>
+</TR>
+</TBODY></TABLE>
+
+
+<P><B>Notes</B></P>
+
+<OL>
+ <LI>The Sling application takes care of constructing the <TT>sling.install.bundles</TT> property from the <TT>sling.install.<n></TT> properties found from the different property sources loaded before launching the framework. The <TT>sling.install.bundles</TT> property needs only be manually created in case the Sling Servlet is not used to launch the OSGi framework for Sling.</LI>
+ <LI>Any <TT>sling.install.<n></TT> property whose start level value <TT><n></TT> is not listed in the <TT>sling.install.bundles</TT> property is ignored.</LI>
+ <LI>The <TT>sling.install.<n></TT> properties are comma-separated lists of bundle specifications where each entry is a tuple of a bundle symbolic name and an optional version range specification (see section 3.2.5, Version Ranges, in the OSGi Service Platform Core Specification). If no version range (or single version) is specified for an entry, any version is applicable.</LI>
+ <LI>The bundles listed in the <TT>sling.install.<n></TT> properties are simple bundles from the point of view of initial installation. If any of the bundles happen to be an Assembly Bundle (see <A href="assembly.html" title="Assembly">Assembly: Bundling Bundles</A>) the Assembly Manager will take care of that bundle after the bundle has been installed.</LI>
+</OL>
+
+
+
+
+<H2><A name="ProvisioningandStartup-ImportantProperties"></A>Important Properties</H2>
+
+<P>To recapitulate here is a list of Framework properties used for initial provisioning:</P>
+
+<TABLE class="confluenceTable"><TBODY>
+<TR>
+<TH class="confluenceTh"> Property </TH>
+<TH class="confluenceTh"> Description </TH>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>obr.repository.url</TT> </TD>
+<TD class="confluenceTd"> A comma-separated list of OSGi Bundle Repository URLs. This property is required to access the OSGi Bundle Repository to install the bundles listed in the <TT>sling.install.<n></TT> properties. See the <TT>org.apache.felix.bundlerepository</TT> Bundle documentation for more information on this property. </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>sling.install.bundles</TT> </TD>
+<TD class="confluenceTd"> A comma-separated list of start level numbers referring to <TT>sling.install.<n></TT> properties listing bundles to install. If this property is empty or missing, nothing will be installed. </TD>
+</TR>
+<TR>
+<TD class="confluenceTd"> <TT>sling.install.<n></TT> </TD>
+<TD class="confluenceTd"> A comma-separated list of bundle specifications consisting of the (required) bundle symbolic name and an (optional) version range specification separated by colon. Any <TT>sling.install.<n></TT> property whose start level value <TT><n></TT> is not listed in the <TT>sling.install.bundles</TT>, property is ignored. </TD>
+</TR>
+</TBODY></TABLE>
+
+
+
+<H2><A name="ProvisioningandStartup-UsingtheSlingStandaloneApplication"></A>Using the Sling Standalone Application</H2>
+
+<P>The Sling Standalone Application is available as an executable JAR file and may be started by just specifying a simple command line:</P>
+
+<DIV class="preformatted"><DIV class="preformattedContent">
+<PRE>$ java -jar sling-app.jar
+</PRE>
+</DIV></DIV>
+
+<P>This causes Sling to start up as described above. The configuration built into the Sling Standalone Application causes the Apache Felix <EM>http.jetty</EM> bundle to be installed to run an embedded Servlet Container backing the OSGi HTTPService implementation used to provide the Sling Management Console.</P>
+
+
+
+<H2><A name="ProvisioningandStartup-UsingtheSlingWebApplication"></A>Using the Sling Web Application</H2>
+
+<P>Launching Sling in a servlet container is equally simple as using the standalone application: Grab the <EM>sling-servlet</EM> web application and deploy it into your favourite servlet container.</P>
+ <DIV class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
+Last modified by fmeschbe on 2009-04-13 14:13:27.0
+ </DIV>
+ </DIV>
+ </BODY>
+</HTML>
+
Added: websites/staging/sling/trunk/content/site/release-management.html
==============================================================================
--- websites/staging/sling/trunk/content/site/release-management.html (added)
+++ websites/staging/sling/trunk/content/site/release-management.html Wed Dec 12 09:16:44 2012
@@ -0,0 +1,491 @@
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<HTML>
+ <HEAD>
+ <TITLE>Apache Sling - Release Management</TITLE>
+ <LINK rel="stylesheet" href="http://sling.apache.org/site/media.data/site.css" type="text/css" media="all">
+ <LINK rel="icon" href="http://sling.apache.org/site/media.data/favicon.ico">
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ </HEAD>
+ <BODY>
+ <DIV class="title">
+ <DIV class="logo">
+ <A href="http://sling.apache.org/site/index.html">
+ <IMG border="0" alt="Apache Sling" src="http://sling.apache.org/site/media.data/logo.png">
+ </A>
+ </DIV>
+ <DIV class="header">
+ <A href="http://www.apache.org/">
+ <IMG border="0" alt="Apache" src="http://sling.apache.org/site/media.data/apache.png">
+ </A>
+ </DIV>
+ </DIV>
+ <DIV class="menu">
+<P><B>Documentation</B><BR class="atl-forced-newline">
+<A href="getting-started.html" title="Getting Started">Getting Started</A><BR class="atl-forced-newline">
+<A href="the-sling-engine.html" title="The Sling Engine">The Sling Engine</A><BR class="atl-forced-newline">
+<A href="development.html" title="Development">Development</A><BR class="atl-forced-newline">
+<A href="bundles.html" title="Bundles">Bundles</A><BR class="atl-forced-newline">
+<A href="tutorials-how-tos.html" title="Tutorials & How-Tos">Tutorials & How-Tos</A><BR class="atl-forced-newline">
+<A href="configuration.html" title="Configuration">Configuration</A><BR class="atl-forced-newline">
+<A href="http://sling.apache.org/apidocs/sling6/index.html" class="external-link" rel="nofollow">API docs</A><BR class="atl-forced-newline">
+<A href="http://s.apache.org/sling.wiki" class="external-link" rel="nofollow">Wiki</A><BR class="atl-forced-newline">
+<A href="http://s.apache.org/sling.faq" class="external-link" rel="nofollow">FAQ</A><BR class="atl-forced-newline"></P>
+
+<P><B>Project info</B><BR class="atl-forced-newline">
+<A href="http://sling.apache.org/site/downloads.cgi" class="external-link" rel="nofollow">Downloads</A><BR class="atl-forced-newline">
+<A href="http://www.apache.org/licenses/" class="external-link" rel="nofollow">License</A><BR class="atl-forced-newline">
+<A href="contributing.html" title="Contributing">Contributing</A><BR class="atl-forced-newline">
+<A href="news.html" title="News">News</A><BR class="atl-forced-newline">
+<A href="links.html" title="Links">Links</A><BR class="atl-forced-newline">
+<A href="project-information.html" title="Project Information">Project Information</A><BR class="atl-forced-newline">
+<A href="https://issues.apache.org/jira/browse/SLING" class="external-link" rel="nofollow">Issue Tracker</A><BR class="atl-forced-newline">
+<A href="http://svn.apache.org/viewvc/sling/trunk" class="external-link" rel="nofollow">Browse Source Repository</A><BR class="atl-forced-newline">
+<A href="security.html" title="Security">Security</A><BR class="atl-forced-newline"></P>
+
+<P><B>Sponsorship</B><BR class="atl-forced-newline">
+<A href="http://www.apache.org/foundation/thanks.html" class="external-link" rel="nofollow">Thanks</A><BR class="atl-forced-newline">
+<A href="http://www.apache.org/foundation/sponsorship.html" class="external-link" rel="nofollow">Become a Sponsor</A><BR>
+<A href="http://www.apache.org/foundation/buy_stuff.html" class="external-link" rel="nofollow">Buy Stuff</A></P>
+
+
+ <IFRAME src="http://www.apache.org/ads/button.html" style="border-width:0; float: left" frameborder="0" scrolling="no" width="135" height="135"></IFRAME>
+ <P style="height: 135px"></P>
+ </DIV>
+ <DIV class="main">
+ <DIV class="breadcrump" style="font-size: 80%;">
+<A href="apache-sling.html" title="Apache Sling Website">Apache Sling Website</A> > <A href="apache-sling.html" title="Apache Sling">Apache Sling</A> > <A href="documentation.html" title="Documentation">Documentation</A> > <A href="development.html" title="Development">Development</A> > <A href="" title="Release Management">Release Management</A>
+ </DIV>
+<H1><A name="ReleaseManagement-ReleaseManagement"></A>Release Management</H1>
+
+
+<P>Sling releases (and SNAPSHOTS) are deployed to the <A href="http://repository.apache.org/" class="external-link" rel="nofollow">Nexus repository</A> instead of the traditional deployment via the Maven 2 mirros source on <TT>people.apache.org</TT>. This makes the release process much leaner and simpler. In addtion we can benefit from the Apache Parent POM 6, which has most of the release profile setup built-in.</P>
+
+<P>Most of the hard work of preparing and deploying the release is done by Maven.</P>
+
+<DIV>
+<UL>
+ <LI><A href="#ReleaseManagement-Prerequisites">Prerequisites</A></LI>
+ <LI><A href="#ReleaseManagement-StagingtheReleaseCandidates">Staging the Release Candidates</A></LI>
+ <LI><A href="#ReleaseManagement-StartingtheVote">Starting the Vote</A></LI>
+ <LI><A href="#ReleaseManagement-WaitfortheResults">Wait for the Results</A></LI>
+ <LI><A href="#ReleaseManagement-CancelingtheRelease">Canceling the Release</A></LI>
+ <LI><A href="#ReleaseManagement-PromotingtheRelease">Promoting the Release</A></LI>
+ <LI><A href="#ReleaseManagement-UpdateJIRA">Update JIRA</A></LI>
+ <LI><A href="#ReleaseManagement-CreateanAnnouncement">Create an Announcement</A></LI>
+ <LI><A href="#ReleaseManagement-RelatedLinks">Related Links</A></LI>
+ <LI><A href="#ReleaseManagement-AppendixA%253ACreateandAddyourkeyto">Appendix A: Create and Add your key to http://www.apache.org/dist/sling/KEYS</A></LI>
+ <LI><A href="#ReleaseManagement-AppendixB%253ApreparingreleasesonMacOSX">Appendix B: preparing releases on Mac OS X</A></LI>
+ <LI><A href="#ReleaseManagement-AppendixC%253ADeploybundlesontheSlingOBR">Appendix C: Deploy bundles on the Sling OBR</A></LI>
+</UL></DIV>
+
+
+
+<H2><A name="ReleaseManagement-Prerequisites"></A>Prerequisites</H2>
+
+<UL>
+ <LI>To prepare or perform a release you <B>MUST BE</B> at least be an Apache Sling Committer.</LI>
+ <LI>Each and every release must be signed; therefore the public key should be cross signed by other Apache committers (not required but suggested) and this public key should be added to <A href="http://www.apache.org/dist/sling/KEYS" class="external-link" rel="nofollow">http://www.apache.org/dist/sling/KEYS</A> and either on pool.sks-keyservers.net or pgp.mit.edu (See Appendix A)</LI>
+ <LI>When preparing the release on Mac OS X, check out Appendix B before trying the steps in the next chapter.</LI>
+ <LI>Make sure you have all Apache servers defined in your <A href="http://maven.apache.org/developers/committer-settings.html" class="external-link" rel="nofollow">settings.xml</A></LI>
+ <LI>Check Jira if all issues for this version have been resolved. If not these need either to be moved to a new version or be fixed for the release first <IMG class="emoticon" src="https://cwiki.apache.org/confluence/images/icons/emoticons/smile.gif" height="20" width="20" align="absmiddle" alt="" border="0"></LI>
+</UL>
+
+
+<P><B>Note</B>: Listing the Apache servers in the <TT>settings.xml</TT> 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" class="external-link" rel="nofollow">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 6, 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 <TT>${user.home}/.m2/settings.xml</TT>:</P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-xml">
+<SPAN class="code-tag"><settings></SPAN>
+ ...
+ <SPAN class="code-tag"><profiles></SPAN>
+ <SPAN class="code-tag"><profile></SPAN>
+ <SPAN class="code-tag"><id></SPAN>apache-release<SPAN class="code-tag"></id></SPAN>
+ <SPAN class="code-tag"><properties></SPAN>
+ <SPAN class="code-tag"><gpg.passphrase></SPAN> <SPAN class="code-tag"><SPAN class="code-comment"><!-- YOUR KEY PASSPHRASE --></SPAN></SPAN> <SPAN class="code-tag"></gpg.passphrase></SPAN>
+ <SPAN class="code-tag"></properties></SPAN>
+ <SPAN class="code-tag"></profile></SPAN>
+ <SPAN class="code-tag"></profiles></SPAN>
+ ...
+<SPAN class="code-tag"></settings></SPAN>
+</PRE>
+</DIV></DIV>
+
+<P>Everything else has been configured in the latest Sling Parent POM:</P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-xml">
+<SPAN class="code-tag"><parent></SPAN>
+ <SPAN class="code-tag"><groupId></SPAN>org.apache.sling<SPAN class="code-tag"></groupId></SPAN>
+ <SPAN class="code-tag"><artifactId></SPAN>sling<SPAN class="code-tag"></artifactId></SPAN>
+ <SPAN class="code-tag"><version></SPAN>6<SPAN class="code-tag"></version></SPAN>
+<SPAN class="code-tag"></parent></SPAN>
+</PRE>
+</DIV></DIV>
+
+
+
+<H2><A name="ReleaseManagement-StagingtheReleaseCandidates"></A>Staging the Release Candidates</H2>
+
+<P>First prepare your POMs for release:</P>
+
+<OL>
+ <LI>Make sure there are no snapshots in the POMs to be released</LI>
+ <LI>Check that your POMs will not lose content when they are rewritten during the release process
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ mvn release:prepare -DdryRun=true
+</PRE>
+</DIV></DIV>
+<P>Compare the original <TT>pom.xml</TT> with the one called <TT>pom.xml.tag</TT> to see if the license or any other info has been removed. This has been known to happen if the starting <TT><project></TT> tag is not on a single line. The only things that should be different between these files are the <TT><version></TT> and <TT><scm></TT> elements. If there are any other changes, you must fix the original <TT>pom.xml</TT> file and commit before proceeding with the release.</P></LI>
+ <LI>Publish a snapshot
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ mvn deploy
+...
+[INFO] [deploy:deploy]
+[INFO] Retrieving previous build number from apache.snapshots.https
+...
+</PRE>
+</DIV></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 <B>Prerequisites</B></LI>
+ <LI>Be sure that the generated artifacts respect the Apache release <A href="http://www.apache.org/dev/release.html" class="external-link" rel="nofollow">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/sling" class="external-link" rel="nofollow">snapshot</A> repository on Apache</LI>
+ </UL>
+ </LI>
+ <LI>Prepare the release
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ mvn release:clean
+$ mvn release:prepare
+</PRE>
+</DIV></DIV>
+ <UL>
+ <LI>Preparing the release will create the new tag in SVN, automatically checking in on your behalf</LI>
+ <LI>If you get a build failure because of an SVN commit problem (namely <EM>The specified baseline is not the latest baseline, so it may not be checked out.</EM>), just repeat the <TT>mvn release:prepare</TT> command until SVN is happy. This is based on a known timing issue when using the European SVN mirror.</LI>
+ </UL>
+ </LI>
+ <LI>Stage the release for a vote
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ mvn release:perform
+</PRE>
+</DIV></DIV>
+ <UL>
+ <LI>The release will automatically be inserted into a temporary staging repository for you, see the Nexus <A href="http://www.sonatype.com/books/nexus-book/reference/staging.html" class="external-link" rel="nofollow">staging documentation</A> for full details</LI>
+ <LI>You can continue to use <TT>mvn release:prepare</TT> and <TT>mvn release:perform</TT> on other sub-projects as necessary on the same machine and they will be combined in the same staging repository - this is useful when making a release of multiple Sling modules.</LI>
+ </UL>
+ </LI>
+ <LI>Close the staging repository
+ <UL>
+ <LI>Login to <A href="https://repository.apache.org/" class="external-link" rel="nofollow">https://repository.apache.org</A> using your Apache SVN credentials. Click on <B>Staging</B> on the left. Then click on <B>org.apache.sling</B> in the list of repositories. In the panel below you should see an open repository that is linked to your username and IP. Right click on this repository and select <B>Close</B>. This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything</LI>
+ </UL>
+ </LI>
+ <LI>Verify the staged artifacts
+ <UL>
+ <LI>If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If you don't like the content of the repository, right click your repository and choose <B>Drop</B>. You can then rollback your release (see <B>Canceling the Release</B>) and repeat the process</LI>
+ <LI>Note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email</LI>
+ </UL>
+ </LI>
+</OL>
+
+
+
+
+<H2><A name="ReleaseManagement-StartingtheVote"></A>Starting the Vote</H2>
+
+<P>Propose a vote on the dev list with the closed issues, the issues left, and the staging repository - for example:</P>
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>To: "Sling Developers List" <dev@sling.apache.org>
+Subject: [VOTE] Release Apache Sling ABC version X.Y.Z
+
+Hi,
+
+We solved N issues in this release:
+https://issues.apache.org/jira/browse/SLING/fixforversion/...
+
+There are still some outstanding issues:
+https://issues.apache.org/jira/browse/SLING/component/...
+
+Staging repository:
+https://repository.apache.org/content/repositories/orgapachesling-[YOUR REPOSITORY ID]/
+
+You can use this UNIX script to download the release and verify the signatures:
+http://svn.apache.org/repos/asf/sling/trunk/check_staged_release.sh
+
+Usage:
+sh check_staged_release.sh [YOUR REPOSITORY ID] /tmp/sling-staging
+
+Please vote to approve this release:
+
+ [ ] +1 Approve the release
+ [ ] 0 Don't care
+ [ ] -1 Don't release, because ...
+
+This vote will be open for 72 hours.
+</PRE>
+</DIV></DIV>
+
+
+
+<H2><A name="ReleaseManagement-WaitfortheResults"></A>Wait for the Results</H2>
+
+<P>From <A href="http://www.apache.org/foundation/voting.html" class="external-link" rel="nofollow">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>
+
+
+<P>The list of binding voters is available on the <A href="project-team.html" title="Project Team">Project Team</A> page.</P>
+
+
+<P>If the vote is successful, post the result to the dev list - for example:</P>
+
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>To: "Sling Developers List" <dev@sling.apache.org>
+Subject: [RESULT] [VOTE] Release Apache Sling ABC version X.Y.Z
+
+Hi,
+
+The vote has passed with the following result :
+
++1 (binding): <<list of names>>
++1 (non binding): <<list of names>>
+
+I will copy this release to the Sling dist directory and
+promote the artifacts to the central Maven repository.
+</PRE>
+</DIV></DIV>
+
+<P>Be sure to include all votes in the list and indicate which votes were binding. Consider -1 votes very carefully. While there is technically no veto on release votes, there may be reasons for people to vote -1. So sometimes it may be better to cancel a release when someone, especially a member of the PMC, votes -1.</P>
+
+<P>If the vote is unsuccessful, you need to fix the issues and restart the process - see <B>Canceling the Release</B>.</P>
+
+<P>If the vote is successful, you need to promote and distribute the release - see <B>Promoting the Release</B>.</P>
+
+
+
+<H2><A name="ReleaseManagement-CancelingtheRelease"></A>Canceling the Release</H2>
+
+<P>If the vote fails, or you decide to redo the release:</P>
+
+<OL>
+ <LI>Remove the release tag from Subversion (<TT>svn del ...</TT>)</LI>
+ <LI>Login to <A href="https://repository.apache.org/" class="external-link" rel="nofollow">https://repository.apache.org</A> using your Apache SVN credentials. Click on <B>Staging</B> on the left. Then click on <B>org.apache.sling</B> in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select <B>Close</B>). Right click on this repository and select <B>Drop</B>.</LI>
+ <LI>Rollback the version in the <TT>pom.xml</TT> and commit any fixes you need to make</LI>
+</OL>
+
+
+
+
+<H2><A name="ReleaseManagement-PromotingtheRelease"></A>Promoting the Release</H2>
+
+<P>If the vote passes:</P>
+
+<OL>
+ <LI>Copy the released artifacts to the Sling dist directory (<TT>/x1/www/www.apache.org/dist/sling</TT>) on <TT>people.apache.org</TT>. This folder is replicated to <A href="http://www.apache.org/dist/sling/" class="external-link" rel="nofollow">http://www.apache.org/dist/sling/</A> a few times a day.</LI>
+ <LI>Delete the old release from the Sling dist directory (it's archived)</LI>
+ <LI>Login to <A href="https://repository.apache.org/" class="external-link" rel="nofollow">https://repository.apache.org</A> with your Apache SVN credentials. Click on <B>Staging</B>. Find your closed staging repository and select it by checking the select box. Select the <B>Releases</B> repository from the drop-down list and click <B>Release</B> from the menu above.</LI>
+ <LI>Once the release is promoted click on <B>Repositories</B>, select the <B>Releases</B> repository and validate that your artifacts are all there.</LI>
+ <LI>If you're releasing bundles, you should also add them to the Sling Release OBR (see <B>Appendix C</B>).</LI>
+ <LI>Update the news section on the website at <A href="news.html" title="News">News</A>.</LI>
+ <LI>Update the download page on the website at <A href="downloads.html" title="Downloads">Downloads</A> to point to the new release.</LI>
+</OL>
+
+
+<P>For the last two tasks, it's better to give the mirrors some time to distribute the uploaded artifacts (one day should be fine). This ensures that once the website (news and download page) is updated, people can actually download the artifacts.</P>
+
+
+
+<H2><A name="ReleaseManagement-UpdateJIRA"></A>Update JIRA</H2>
+
+<P>Go to <A href="https://issues.apache.org/jira/plugins/servlet/project-config/SLING/versions" class="external-link" rel="nofollow">Manage Versions</A> section on the SLING JIRA and mark the X.Y.Z version as released setting the release date to the date the vote has been closed.</P>
+
+<P>Close all issues of the released version.</P>
+
+<P>Also create a new version X.Y.Z+2, if that hasn't already been done.</P>
+
+
+
+<H2><A name="ReleaseManagement-CreateanAnnouncement"></A>Create an Announcement</H2>
+
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>To: "Sling Developers List" <dev@sling.apache.org>, "Apache Announcements" <announce@apache.org>
+Subject: [ANN] Apache Sling ABC version X.Y.Z Released
+
+The Apache Sling team is pleased to announce the release of Apache Sling ABC version X.Y.Z
+
+Apache Sling is a web framework that uses a Java Content Repository, such as Apache Jackrabbit, to store and manage content. Sling applications use either scripts or Java servlets, selected based on simple name conventions, to process HTTP requests in a RESTful way.
+
+<<insert short description of the sub-project>>
+
+http://sling.apache.org/site/apache-sling-ABC.html
+
+This release is available from http://sling.apache.org/site/downloads.cgi and Maven:
+
+<dependency>
+ <groupId>org.apache.sling</groupId>
+ <artifactId>org.apache.sling.ABC</artifactId>
+ <version>X.Y.Z</version>
+</dependency>
+
+
+Release Notes:
+
+<<insert release notes in text format from JIRA>>
+
+Enjoy!
+
+-The Sling team
+</PRE>
+</DIV></DIV>
+
+
+<P><B>Important</B>: Add the release to the Software section of the next board report below <A href="../SLING/reports.html" class="external-link" rel="nofollow">Reports</A>.</P>
+
+
+
+<H2><A name="ReleaseManagement-RelatedLinks"></A>Related Links</H2>
+
+<OL>
+ <LI><A href="http://www.apache.org/dev/release-signing.html" class="external-link" rel="nofollow">http://www.apache.org/dev/release-signing.html</A></LI>
+ <LI><A href="http://wiki.apache.org/incubator/SigningReleases" class="external-link" rel="nofollow">http://wiki.apache.org/incubator/SigningReleases</A></LI>
+</OL>
+
+
+
+
+<H2><A name="ReleaseManagement-AppendixA%3ACreateandAddyourkeyto"></A>Appendix A: Create and Add your key to <A href="http://www.apache.org/dist/sling/KEYS" class="external-link" rel="nofollow">http://www.apache.org/dist/sling/KEYS</A></H2>
+
+<P>Considering that you are using a *nix system with a working OpenSSH, GnuPG, and bash you can create and add your own key with the following command:</P>
+
+<OL>
+ <LI><EM>Create a public/private pair key</EM>:
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ gpg --gen-key
+</PRE>
+</DIV></DIV>
+<P>When gpg asks for e-mail linked the key you <B>MUST USE</B> the <committer>@apache.org one<BR>
+When gpg asks for comment linked the key you <EM>SHOULD USE</EM> "CODE SIGNING KEY"</P></LI>
+ <LI><EM>Add the key to</EM> <A href="http://www.apache.org/dist/sling/KEYS:" class="external-link" rel="nofollow">http://www.apache.org/dist/sling/KEYS:</A> type the following command replacing the word e-mail with your Apache's one (<committer>@apache.org).
+<DIV class="preformatted panel" style="border-width: 1px;"><DIV class="preformattedContent panelContent">
+<PRE>$ (gpg --list-sigs e-mail && gpg --export --armor e-mail) > toadd.key
+$ scp toadd.key people.apache.org:
+$ ssh people.apache.org "cat toadd.key >> /x1/www/www.apache.org/dist/sling/KEYS"
+</PRE>
+</DIV></DIV></LI>
+ <LI>You are <B>DONE</B>, but to see the changes on <A href="http://www.apache.org/dist/sling/KEYS" class="external-link" rel="nofollow">http://www.apache.org/dist/sling/KEYS</A> you must wait 2 hours</LI>
+</OL>
+
+
+<P>You also have to add your public key either on pool.sks-keyservers.net or pgp.mit.edu (for the statging repository).</P>
+
+
+
+<H2><A name="ReleaseManagement-AppendixB%3ApreparingreleasesonMacOSX"></A>Appendix B: preparing releases on Mac OS X</H2>
+
+<P>When running the <TT>mvn release:prepare</TT> command on Mac OS X, you might see the following error:</P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-java">[INFO] Executing: svn --non-interactive commit --file /tmp/maven-scm-802409492.commit --targets /tmp/maven-scm-18804-targets
+[INFO] Working directory: /homedir/dev/sling/dependencymanager
+[INFO] ------------------------------------------------------------------------
+[ERROR] BUILD FAILURE
+[INFO] ------------------------------------------------------------------------
+[INFO] Unable to commit files
+Provider message:
+The svn command failed.
+Command output:
+svn: Commit failed (details follow):
+svn: MKACTIVITY of '/repos/asf/!svn/act/4f11ad5d-9161-0410-b4dd-cb727141ea8c': authorization failed (https:<SPAN class="code-comment">//svn.apache.org)</SPAN></PRE>
+</DIV></DIV>
+
+<P>This is due to a bug in Subversion on the Mac, as described by Brett Porter in his <A href="http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/" class="external-link" rel="nofollow">blog</A>. He proposes putting an "svn" script at the head of your path to fix the issue.</P>
+
+
+
+<H2><A name="ReleaseManagement-AppendixC%3ADeploybundlesontheSlingOBR"></A>Appendix C: Deploy bundles on the Sling OBR</H2>
+
+<P>We are mainting an OSGi Bundle Repository providing all release of the Sling Bundles. This repository is maintained as part of the Apache Sling site and is available at <A href="http://sling.apache.org/obr/sling.xml" class="external-link" rel="nofollow">http://sling.apache.org/obr/sling.xml</A>. The source for this page is maintained in the SVN repository below the <EM>site</EM>, that is at <A href="http://svn.apache.org/repos/asf/sling/site/" class="external-link" rel="nofollow">http://svn.apache.org/repos/asf/sling/site/</A>. To update the Sling OBR repository you must be an Apache Sling Committer since this requires SVN write access.</P>
+
+<P>To update the OBR you may use the Apache Felix Maven Bundle Plugin which prepares the bundle descriptor to be added to the OBR file. Follow these steps to update the OBR:</P>
+
+<P><B>1. Checkout or update the Site Source</B></P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-java">
+$ svn checkout https:<SPAN class="code-comment">//svn.apache.org/repos/asf/sling/site</SPAN>
+</PRE>
+</DIV></DIV>
+
+<P>Note, that you have to checkout the site using the <TT>https</TT> URL, otherwise you will not be able to commit the changes later.</P>
+
+<P><B>2. Deploy the Descriptor</B></P>
+
+<P>To deploy the project descriptor, checkout the tag of the bundle to deploy and run maven</P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-java">
+$ svn checkout http:<SPAN class="code-comment">//svn.apache.org/repos/asf/sling/tags/the_module_tag
+</SPAN>$ mvn clean install \
+ org.apache.felix:maven-bundle-plugin:deploy \
+ -DprefixUrl=http:<SPAN class="code-comment">//repo1.maven.org/maven2 \
+</SPAN> -DremoteOBR=sling.xml \
+ -DaltDeploymentRepository=apache.releases::<SPAN class="code-keyword">default</SPAN>::file:<SPAN class="code-comment">///path_to_site_checkout/obr</SPAN>
+</PRE>
+</DIV></DIV>
+
+<P>This generates the bundle descriptor and adds it to the <TT>sling.xml</TT> file of your site checkout.</P>
+
+
+<P><B>2a. Variant: Refer to Maven Repository</B></P>
+
+<P>Instead of checking out and building the project locally, you may also use the <TT>deploy-file</TT> goal of the Maven Bundle Plugin:</P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-java">
+$ wget http:<SPAN class="code-comment">//repo1.maven.org/maven2/org/apache/sling/the_module/version/the_module-version.jar
+</SPAN>$ wget http:<SPAN class="code-comment">//repo1.maven.org/maven2/org/apache/sling/the_module/version/the_module-version.pom
+</SPAN>$ mvn org.apache.felix:maven-bundle-plugin:deploy-file \
+ -Dfile=the_module-version.jar -DpomFile=the_module-version.pom \
+ -DbundleUrl=http:<SPAN class="code-comment">//repo1.maven.org/maven2/org/apache/sling/the_module/version/the_module-version.jar \
+</SPAN> -Durl=file:<SPAN class="code-comment">///path_to_site_checkout/obr \
+</SPAN> -DprefixUrl=http:<SPAN class="code-comment">//repo1.maven.org/maven2 \
+</SPAN> -DremoteOBR=sling.xml
+$ rm the_module-version.jar the_module-version.pom
+</PRE>
+</DIV></DIV>
+
+
+<P><B>3. Commite the Site Changes</B></P>
+
+<P>In the Site checkout folder commit the changes to the <TT>obr/sling.xml</TT> files (you may also review the changes using the <TT>svn diff</TT> command).</P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-java">
+$ svn commit -m<SPAN class="code-quote">"Add Bundle ABC Version X.Y.Z"</SPAN> obr/sling.xml
+</PRE>
+</DIV></DIV>
+
+
+<P><B>4. Update the Site on</B> <TT><B>people.apache.org</B></TT></P>
+
+<P>After committing the changes, you have to update the site source, which is getting mirrored to the web servers on <TT>people.apache.org</TT></P>
+
+<DIV class="code panel" style="border-width: 1px;"><DIV class="codeContent panelContent">
+<PRE class="code-java">
+$ ssh people.apache.org svn update /x1/www/sling.apache.org/obr/sling.xml
+</PRE>
+</DIV></DIV>
+
+<P>After updating the site source it will generally take an hour or two until the changes are visible on the web.</P>
+ <DIV class="timestamp" style="margin-top: 30px; font-size: 80%; text-align: right;">
+Last modified by cziegeler@apache.org on Fri Jul 06 04:04:26 EDT 2012
+ </DIV>
+ <DIV class="trademarkFooter">
+Apache Sling, Sling, Apache, the Apache feather logo, and the Apache Sling project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.
+ </DIV>
+ </DIV>
+ </BODY>
+</HTML>
+
Added: websites/staging/sling/trunk/content/site/reports.html
==============================================================================
--- websites/staging/sling/trunk/content/site/reports.html (added)
+++ websites/staging/sling/trunk/content/site/reports.html Wed Dec 12 09:16:44 2012
@@ -0,0 +1,49 @@
+
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<HTML>
+ <HEAD>
+ <TITLE>Apache Sling - Reports</TITLE>
+ <LINK rel="stylesheet" href="http://incubator.apache.org/sling/site/media.data/site.css" type="text/css" media="all">
+ <LINK rel="icon" href="http://incubator.apache.org/sling/site/media.data/favicon.ico">
+ <META http-equiv="Content-Type" content="text/html;charset=UTF-8">
+ </HEAD>
+ <BODY>
+ <DIV class="title">
+ <DIV class="logo">
+ <A href="http://incubator.apache.org/sling/site/index.html">
+ <IMG border="0" alt="Apache Sling" src="http://incubator.apache.org/sling/site/media.data/logo.png">
+ </A>
+ </DIV>
+ <DIV class="header">
+ <A href="http://incubator.apache.org/">
+ <IMG border="0" alt="Apache Incubator" src="http://incubator.apache.org/images/apache-incubator-logo.png">
+ </A>
+ </DIV>
+ </DIV>
+ <DIV class="menu">
+ <P>
+
+<UL>
+ <LI><A href="index.html" title="Index">Home</A></LI>
+ <LI><A href="project-information.html" title="Project Information">Project Information</A></LI>
+ <LI><A href="usecases.html" title="UseCases">Use Cases</A></LI>
+ <LI><A href="guides.html" title="Guides">Guides</A></LI>
+ <LI><A href="documentation.html" title="Documentation">Documentation</A></LI>
+ <LI><A href="plugins.html" title="Plugins">Plugins</A></LI>
+ <LI><A href="faq.html" title="FAQ">FAQ</A></LI>
+ <LI><A href="links.html" title="Links">Links</A></LI>
+ <LI><A href="old-documentation.html" title="Old Documentation">Old Documentation</A></LI>
+ <LI><SPAN class="nobr"><A href="http://cwiki.apache.org/confluence/x/GAUB" title="Visit page outside Confluence" rel="nofollow">Wiki<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><SPAN class="nobr"><A href="http://www.apache.org/foundation/thanks.html" title="Visit page outside Confluence" rel="nofollow">Sponsors<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+ <LI><SPAN class="nobr"><A href="http://www.apache.org/foundation/sponsorship.html" title="Visit page outside Confluence" rel="nofollow">Sponsorship<SUP><IMG class="rendericon" src="http://cwiki.apache.org/confluence/images/icons/linkext7.gif" height="7" width="7" align="absmiddle" alt="" border="0"></SUP></A></SPAN></LI>
+</UL>
+
+
+<P>
+ </DIV>
+ <DIV class="main">
+<P>Here you find the all reports submitted to the Incubator PMC as well as the report in preparation for the current report period.</P>
+ </DIV>
+ </BODY>
+</HTML>
+