; Fri, 13 Jul 2012 20:04:43 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r825706 [1/2] - in /websites/staging/ctakes/trunk/content: ./ ctakes/ ctakes/css/ Date: Fri, 13 Jul 2012 20:04:42 -0000 To: ctakes-commits@incubator.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120713200443.4BC6923888FE@eris.apache.org> Author: buildbot Date: Fri Jul 13 20:04:42 2012 New Revision: 825706 Log: Staging update by buildbot for ctakes Added: websites/staging/ctakes/trunk/content/ctakes/community-faqs.html websites/staging/ctakes/trunk/content/ctakes/css/ websites/staging/ctakes/trunk/content/ctakes/css/ctakes.css websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html websites/staging/ctakes/trunk/content/ctakes/downloads.html websites/staging/ctakes/trunk/content/ctakes/get-involved.html websites/staging/ctakes/trunk/content/ctakes/license.html websites/staging/ctakes/trunk/content/ctakes/mailing-lists.html websites/staging/ctakes/trunk/content/ctakes/people.html websites/staging/ctakes/trunk/content/ctakes/ppmc-faqs.html websites/staging/ctakes/trunk/content/ctakes/source.html Modified: websites/staging/ctakes/trunk/content/ (props changed) websites/staging/ctakes/trunk/content/ctakes/sitemap.html Propchange: websites/staging/ctakes/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Jul 13 20:04:42 2012 @@ -1 +1 @@ -1360958 +1361364 Added: websites/staging/ctakes/trunk/content/ctakes/community-faqs.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/community-faqs.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/community-faqs.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,51 @@ + + + + Community FAQs + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

If you want to report a bug, please create issue on our JIRA.

+ +

Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

+ + Added: websites/staging/ctakes/trunk/content/ctakes/css/ctakes.css ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/css/ctakes.css (added) +++ websites/staging/ctakes/trunk/content/ctakes/css/ctakes.css Fri Jul 13 20:04:42 2012 @@ -0,0 +1,357 @@ +/* +* Licensed to the Apache Software Foundation (ASF) under one or more +* contributor license agreements. See the NOTICE file distributed with +* this work for additional information regarding copyright ownership. +* The ASF licenses this file to You 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. +*/ +body { + color: white; + font-family: Helvetica, Arial, 'Liberation Sans', FreeSans, sans-serif; + font-size: 12pt; + margin: 0; +} + +#banner { + height: 150px; + padding: 0 0 0 0; + color: black; + font-family: Helvetica, Arial, 'Liberation Sans', FreeSans, sans-serif; + font-size:16pt; + vertical-align: middle; +} + +#bannerright { + text-align: right; + float: right; + padding: 34pt 36pt 26pt 36pt; +} + +#bannercenter { + padding: 46pt 2pt 50pt 2pt; + float: center; + color: #107EC0; +} + +#bannerleft { + text-align: left; + float: left; +} + +#bannerleft a:hover { + color: #107EC0; + background-color: white; +} + +a { + color: #107EC0; +} + +a:visited { + color: #107EC0; +} + +a:hover { + color: #107EC0; + text-decoration:underline; +} + +a img { border: none; } + +h1,h2,h3,h4,h5,h6 { + color: #193240; + text-transform:uppercase; +} + +#clear { + overflow: auto; + clear: both; +} + +#content { + margin: 0 50px 20px 50px; + padding: 0 8px 40px; + color: #333; + overflow: auto; + clear: both; +} + +#content h1,h2,h3,h4,h5,h6 { + font-weight: normal; + text-transform:none; + margin: 10px 0 15px; + padding: 5px 0; +} + +#content h1 { + font-size: 1.4em; + padding: 15px; + border-top: 1px solid #a3afb6; +} + +#content h2 { + font-size: 1.2em; + margin-top: 2em; +} + +#content h3,h4,h5,h6 { + border-bottom: none; + font-size: 1em; + margin-bottom: 0; +} + +#content li { + margin-bottom: 0.5em; +} + +#contenta { + margin: 0 150px 20px 250px; + padding: 0 8px 40px; + color: #333; +} + +#contenta h1,h2,h3,h4,h5,h6 { + font-weight: normal; + margin: 10px 0 15px; + padding: 5px 0; +} + +#contenta h1 { + font-size: 1.4em; + padding: 15px; + border-top: 1px solid #a3afb6; +} + +#contenta h2 { + font-size: 1.2em; + margin-top: 2em; + border-bottom: 1px solid #a3afb6; +} + +#contenta h3,h4,h5,h6 { + border-bottom: none; + font-size: 1em; + margin-bottom: 0; +} + +#contenta li { + margin-bottom: 0.5em; +} + +#contenta a:hover { + color: #107EC0; + text-decoration:underline; + background-color: #e6ebed; +} + +table { + border-collapse:collapse; + margin: auto; +} + +th { + height: 40px; + background: #f5f8fa; + border: 1px solid #a3afb6; + vertical-align: middle; + font-size: 0.9em; +} + +td { + vertical-align: top; + border: 1px solid #a3afb6; + padding: 0.4em 0.5em 0.4em 0.5em; + font-size: 0.9em; +} + +.w140 { + width: 140px; +} + +.w160 { + width: 160px; +} + +.w180 { + width: 180px; +} + +.w200 { + width: 200px; +} + +.w220 { + width: 220px; +} + +.codehilite { + background-color: #F0F000; + padding: 0.01em 1em; + border-radius: 10px; +} + +#sidenav { + border: 1px solid #e6ebed; + border-left: none; + -moz-border-radius: 0 10px 10px 0; + border-radius: 0 10px 10px 0; + font-size: 0.9em; + color: #003; + float: left; + padding: 15px 15px 5px 25px; + width: 180px; + background: none repeat scroll 0 0 #f5f8fa; + margin: 0 0 20px 0; +} + +#sidenav img { + padding-bottom: 15px; + margin-left: auto; + margin-right: auto; + display: block; +} + +#sidenav h1 { + color: #000; + font-size: 1em; + padding: 0; + margin-top: 0.8em; + margin-bottom: 0; + border-bottom: 1px solid #a3afb6; +} + +#sidenav ul { + margin: 0 0; + padding: 0; + list-style: none; +} + +#sidenav li { + border-bottom: 1px solid #e6ebed; + margin: 0.2em 0; + padding: 0; +} + +#sidenav li a { + margin: 0; + text-decoration:none; +} + +#sidenav li a:hover { + color: #193240; + background: none; +} + +#navigation { + border: 1px solid #e6ebed; + border-left: none; + -moz-border-radius: 0 10px 10px 0; + border-radius: 0 10px 10px 0; + font-size: 0.9em; + color: #003; + float: left; + padding: 15px 15px 5px 25px; + width: 180px; + background: none repeat scroll 0 0 #f5f8fa; + margin: 0 0 20px 0; +} + +#navigation img { + padding-bottom: 15px; + margin-left: auto; + margin-right: auto; + display: block; +} + +#navigation h1 { + color: #000; + font-size: 1em; + padding: 0; + margin-top: 0.8em; + margin-bottom: 0; + border-bottom: 1px solid #a3afb6; +} + +#navigation ul { + margin: 0 0; + padding: 0; + list-style: none; +} + +#navigation li { + border-bottom: 1px solid #e6ebed; + margin: 0.2em 0; + padding: 0; +} + +#navigation li a { + margin: 0; + text-decoration:none; +} + +#navigation li a:hover { + color: #107EC0; + background-color: #e6ebed; +} + +#footera { + margin: 20px 0px 0px 0px; + padding: 8px 0px 12px 0px; + border-top: 2px solid #ccc; + color:#666; + font-size: 8pt; + padding: 0 8px; + text-align: left; + overflow: auto; + clear: both; + line-height: 10pt; +} + +#copyrighta { +} + +#copyrighta p { + padding-left: 20px; + line-height: 10pt; + padding-bottom: 5px; +} + +#copyrighta a { + color: #107EC0; + text-decoration:underline; +} + +#copyrighta a:hover { + background-color: #e6ebed; +} + +#poweredby { + float: right; + text-align: right; + width: 210px; + height: 100px; +} + +#asf-logo { + width: 180px; + padding-top: 20px; +} + + + +/* definition lists */ +dd {} +dl {} +dt { + display: inline; + float: left; +} \ No newline at end of file Added: websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/ctakes-release-guide.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,441 @@ + + + + Release Guide + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

I. Prerequisites

You should read the document:A Guide To Release Management During Incubation (DRAFT).
+
You must have shell access to people.apache.org, such as PuTTY.
+
Release manager must have his public key appended to the KEYS file checked in to SVN and the key published on one of the public key servers.
+ ODF Toolkit project KEYS file: https://svn.apache.org/repos/asf/incubator/odf/trunk/KEYS.
+ The sign tool, such as GnuPG should be installed. More info can be found here: http://www.apache.org/dev/release-signing.html.
+
You must have Oracle JDK 1.5/1.6 or Open JDK.
+
Subversion client is installed. We suggest you install version 1.7.2 or later.
+
The ODF Toolkit build system requires Maven to perform a build. We suggest you install version later than 2.2.1 or 3.0.4.
+

II. Legal Audit

Legal policy and interpretation changes from time to time so it is worth investing a little time reading again the legal release material.
+

Check that dependencies (and in particular those dependencies that ship in the packages) comply with Apache policy. Apache projects may distribute artifacts and documents as part of a release which are not Apache Licensed. All such artifacts must comply with Apache's 3rd party licensing policy.
+ All the licenses on all the files to be included within a package should be included in the LICENSE document.
+
The NOTICE document is for additional copyright and attribution statements those licenses may require. A typical NOTICE document at a minimum includes a copyright and attribution statement for The Apache Software Foundation. Nothing else belongs in the NOTICE document.
+
It is good practice to check the provenance of any source documents which do not have license headers. With the help of RAT, you can run Maven command: 'mvn verify -Ppedantic' on the "trunk" to get a report about the license header.
+
Make sure every committer have a signed Contributor License Agreement (CLA) on file. It's a contract between a contributor and Apache granting Apache rights to code contributed.
+
If any dependencies are cryptographic libraries then it may be necessary to fill in some paperwork to make sure they are compliance with US export regulations.
+

III. Release Document

Documents a particular release of a product rather than the product itself. For a release manager, the first thing he should do is to consult and correct the project's release documentation. For ODF Toolkit, we should make sure the following items are ready.
+

Ensure the CHANGES.txt is up to date.
+
The Cookbook was updated to support the new release, add new content and modify the old parts.
+
Make sure all of the demo codes work well under the new release. If necessary, write new demo to introduce the key new features in the new version.
+
Remember to update the online Javadoc to the newest version, but don't publish until the vote pass.
+
Prepare other website update content, save them as staged, but don't publish until the vote pass.
+

IV. Release Candidate

A release candidate is a set of artifacts upon which a vote is held for a release. The actual nature of the release candidate depends on the release system adopted by a the project. For ODF Toolkit, we supply 3 type of artifacts, binary package, source package and document package. Making release artefacts should follow the following steps:
+

+
Update version id in pom.xml.
+
+
<groupId>org.apache.odftoolkit</groupId>
+<artifactId>odftoolkit</artifactId>
+<version>0.6-incubating-SNAPSHOT</version>
+
The version should include incubating (or incubator) to ensure that the artifacts created comply with Incubator release policy.
+
+
+
Tag current version.
+ Include the current revision number in the comment.
+
+
$ svn cp https://svn.apache.org/repos/asf/incubator/odf/trunk/ \
+https://svn.apache.org/repos/asf/incubator/odf/tags/$TAG \
+-m "tag r649911 as odftoolkit-0.5-incubating"
+
Where $TAG is the release tag, for example, odftoolkit-0.5-incubating.
+
+
+
Checkout the tagged version.
+
+
cd tags
+svn checkout https://svn.apache.org/repos/asf/incubator/odf/tags/$TAG
+
+
+
Build artifacts.
+
+
cd $TAG
+mvn install
+
+
+
Package artifacts
+ Comment the following snippet in pom.xml to avoid duplicated package in sub-components:
+ <modules>
+ <module>taglets</module>
+ <module>generator</module>
+ <module>xslt-runner</module>
+ <module>xslt-runner-task</module>
+ <module>odfdom</module>
+ <module>validator</module>
+ <module>simple</module>
+ </modules>
+
+

Remove the comments of the following snippet in pom.xml to make sure Maven know how to package:
+

Replace "${user.name}" with your Apache ID, such as "devinhan".       
+Use the following command to package.
+
+mvn install -Papache-release
+
+After package you should have the following files in the "target\":
+
+  $TAG-bin.tar.bz2    
+  $TAG-bin.tar.gz   
+  $TAG-bin.zip   
+  $TAG-src.tar.bz2    
+  $TAG-src.tar.gz    
+  $TAG-src.zip    
+  $TAG-doc.tar.bz2    
+  $TAG-doc.tar.gz   
+  $TAG-doc.zip   
+  *.asc   
+  *.md5   
+  *.sha   
+  vote.txt
+
+vote.txt is a draft of the dev vote mail. Each package has its own .asc, .md5 and .asc files.
+

+ + +

+
Upload artifacts for vote.
+ Login people.apache.org using your Apache LDAP account. Copy the artifacts packages to directory "/public_html/odftoolkit-release/$TAG" using scp. If the directly don't exist, please create. It is best to scp into the home directory and then copy into position from there.
+ Make sure all of the files are owned by the incubator group, group readable and writable, and read only for the world. In short -rw-rw-r--. To do this from the top level:
+
+
```
  > find . -type f -exec chmod 664 {} \;     
+  > find . -type d -exec chmod 775 {} \;  
+  > chgrp -R incubator *
+
```
+ + +
Then the artifacts can be accessed from Web browser. The link looks like:
+
+
http://people.apache.org/~$USER/odftoolkit-release/$TAG
+
+
Replace $USER with your Apache ID, such as "devinhan".
+
+

V. Incubator Release Vote

After release candidate is uploaded, the release manager can start vote process. All releases by podlings must be approved by the Incubator PMC. The conventional process is for the podling to follow the usual Apache process release vote and then call for a Incubator PMC VOTE on the general incubator list.
+

+
Vote in ODF Toolkit Development List
+A formal vote on candidate artifacts must be conducted by the release manager on the ODF Toolkit development list. The vote mail can be drafted based on the vote.txt, which is generated with artifacts. A sample looks like this:
+
+
Subject: [VOTE] Release Apache ODF Toolkit 0.5-incubating(RC6)
+ To: odf-dev@incubator.apache.org
+ Hi all,
+ Please vote on releasing the following candidate as Apache ODF Toolkit (incubating) version 0.5. + This will be the first incubator release for ODF Toolkit in Apache.
+
+
This release candidate fixes the following issues found in RC5:
+ (1) Reomve JUnit declaration from NOTICE & LICENSE files.
+ (2) Fix the "mvn clean" failed issue.
+
+
The candidate for the ODF Toolkit 0.5-incubating release is available at:
+ http://people.apache.org/~devinhan/odftoolkit-release/odftoolkit-0.5-incubating-rc6/
+
+
The release candidate is a zip archive of the sources in:
+ https://svn.apache.org/repos/asf/incubator/odf/tags/odftoolkit-0.5-incubating/
+
+
The SHA1 checksum of the archive is 44e16d8ee39fc0426f96aa7da9cd8eefccaf78e5.
+ The MD5 checksum of the archive is c12a87f0ca441f23d945a423e1d4127c.
+
+
Besides source code, binary packages and javadoc packages are also listed in:
+ http://people.apache.org/~devinhan/odftoolkit-release/odftoolkit-0.5-incubating-rc6/
+
+
All of the artifacts supply three package formats, tar.gz, tar.bz2 and zip.
+
+
Keys:
+ http://www.apache.org/dist/incubator/odftoolkit/KEYS
+
+
Please vote on releasing this package as Apache ODF Toolkit 0.5-incubating.
+ The vote is open for the next full week, until next Saturday, Dec 31rd 6pm, because of the Christmas holiday, and passes + if a majority of at least 3 +1 IPMC votes are cast.
+ [ ] +1 Release this package as Apache ODF Toolkit 0.5-incubating
+ [ ] -1 Do not release this package because...
+ To learn more about Apache ODF Toolkit, please access: http://incubator.apache.org/odftoolkit/.
+
+

All votes are welcome, but only those votes by the project's PPMC members (or IPMC members) count towards the final tally. The voting period should be no less than 72 hours, and at the end of the voting the release manager should post a final tally to the list. eg.
+

  Subject: [RESULT][VOTE] Release Apache ODF Toolkit 0.5-incubating-rc7          
+      To: odf-dev@incubator.apache.org
+
+  Hi All,        
+  The RC7 ballot has ended (due to New Year Holiday, we extended the vote to this Monday ) with the following results:
+
+  From PPMC members:    
+  +1 daisyguo     
+  +1 devinhan   
+  +1 robweir       
+  +1 svanteschubert
+
+  From Mentors:      
+  +1 yegor(IPMC)
+
+  Other votes:     
+   (abstain non-binding [;<) orcmid
+
+  I will send a vote mail to incubator-general mail list and collect another 2 IPMC +1's votes.     
+  Thanks all of the voters.
+
+  The vote passes if there are at least 3 +1's from the PPMC/IPMC members and more +1's than -1's. This is what is meant by majority consensus. If you've gotten this far, congratulations, you're nearly ready to upload and announce the release.     
+  If the vote is failed, the release manager should improve the artifacts based on the comments and prepare new candidate. That means step "III. Release Candidate" need to rework. This process maybe repe
 at several times until the vote passes.        
+  **NOTE:** Please remember to delete old release candidates from Apache home space after new candidates are uploaded.
+

+ + +

Vote in General Incubator List
+In the case of the incubator, the IPMC must approve all releases. That means there is an additional bit of voting that the release manager must now oversee on general@incubator in order to gain that approval. The release manager must inform general@incubator that the vote has passed on the project's development list, and should indicate any IPMC votes gained during that process. A new vote on the release candidate artifacts must now be held on general@incubator to seek majority consensus from the IPMC. Previous IPMC votes issued on the project's development list count towards that goal. The sample mail is:
+

Subject: [VOTE] Release Apache ODF Toolkit 0.5-incubating(RC7)
+ To: general@incubator.apache.org
+ Cc: odf-dev@incubator.apache.org
+ Hi all,
+

  The ODF Toolkit 0.5 is ready for release.  This will be our first incubator release.     
+  We had a preliminary vote in the PPMC, which had great results, including a +1 from our mentor, Yegor.
+
+  The PPMC vote result thread is here:    
+  http://markmail.org/message/tw3juzkak6kdiod2       
+  The vote thread is here:     
+  http://markmail.org/message/h6qfmhl4vulyjyhw
+
+  We need two more IPMC votes to pass.
+
+  Please vote on releasing the following candidate RC7 as Apache ODF Toolkit (incubating) version 0.5.
+
+  This release candidate fixes the pom.xml file inconsistant issue found in RC6. Thanks Yegor!
+
+  The candidate for the ODF Toolkit 0.5-incubating release is available at:   
+  http://people.apache.org/~devinhan/odftoolkit-release/odftoolkit-0.5-incubating-rc7/
+
+  The release candidate is a zip archive of the sources in:        
+  https://svn.apache.org/repos/asf/incubator/odf/tags/odftoolkit-0.5-incubating/
+
+  The SHA1 checksum of the zip archive is 4e97a1a79291035d590b5578caf79478dc3f6de8.      
+  The MD5 checksum of the zip archive is 8883f036ee34282077d3c175329f6257.
+
+  Besides source code, binary packages and javadoc packages are also listed in:     
+  http://people.apache.org/~devinhan/odftoolkit-release/odftoolkit-0.5-incubating-rc7/
+
+  All of the artifacts supply three package formats, tar.gz, tar.bz2 and zip.
+
+  Keys:   
+  http://www.apache.org/dist/incubator/odftoolkit/KEYS
+
+  The vote is open for 72 hours, or until we get the needed number of votes (3 +1).
+
+    [ ] +1 Release this package as Apache ODF Toolkit 0.5-incubating      
+    [ ] -1 Do not release this package because...
+
+  To learn more about Apache ODF Toolkit, please access http://incubator.apache.org/odftoolkit/.
+

+ + +

Once the 72-hour minimum voting period has ended on general@incubator, the release manager should tally the votes and declare a result. If majority consensus has been achieved with respect to IPMC votes, the release manager may proceed with the release. Otherwise, the release manager need to rework step(III) and step(IV) based on the received comments.
+ The vote result mail looks like:
+

      Subject: [VOTE] Release Apache ODF Toolkit 0.5-incubating(RC7)           
+           To: general@incubator.apache.org, odf-dev@incubator.apache.org         
+      Hi all,
+
+      The Apache ODF Toolkit 0.5-incubating RC7 ballot has ended. We have received 4 IPMC +1 votes (plus an additional 4 PPMC +1   votes)       
+      during the release voting on dev and general. The vote passed!
+
+      Results:
+
+      From IPMC members:       
+               name                     apache id        
+            +1 Yegor Kozlov(mentor)       yegor        
+            +1 Nick Burch(mentor)         nick          
+            +1 Chris Mattmann             mattmann       
+            +1 Christian Grobmeier        grobmeier
+
+      From PPMC members:        
+               name                      apache id      
+            +1  Ying Chung Guo              daisyguo        
+            +1  Biao Han                    devinhan      
+            +1  Rob Weir                    robweir        
+            +1  Svante Schubert             svanteschubert
+
+      Other votes:      
+                                        name                       apache id      
+            (abstain non-binding [;<)   Dennis E. Hamilton        orcmid
+
+       We will work on releasing ODF Toolkit 0.5. Thank you everyone who worked in this release!
+

+ + +

VI. After the Vote

+
Distributing Releases
+ The distribution upload location (www.apache.org/dist) for all Apache projects is the /www/www.apache.org/dist directory on people.apache.org. Each project (including the Incubator) owns a directory within dist.
+ The directory of ODF Toolkit is http://www.apache.org/dist/incubator/odftoolkit/. The release manager should move the release artifacts from /public_html/odftoolkit-release/$TAG to this directory.
+
+
+
Mirroring
+ To avoid excessive use of bandwidth and to increase download speeds, official releases are made available through a global network of volunteer mirrors. Using these mirrors has some notable differences from unmirrored downloads. In particular, a <a href="http://www.apache.org/dev/release-download-pages.html" script</a must be used to direct the download to an appropriate URL. The mdtext format sample is:
+
+
**Current Version (0.5-incubating)**
+ * Source:
+ * [odftoolkit-0.5-incubating-src.tar.gz](http://www.apache.org/dyn/closer.cgi/incubator/odftoolkit/sources/odftoolkit-0.5-incubating-src.tar.gz)
+ [[asc](http://www.apache.org/dist/incubator/odftoolkit/sources/odftoolkit-0.5-incubating-src.tar.gz.asc)]
+ [[md5](http://www.apache.org/dist/incubator/odftoolkit/sources/odftoolkit-0.5-incubating-src.tar.gz.md5)]
+ [[sha](http://www.apache.org/dist/incubator/odftoolkit/sources/odftoolkit-0.5-incubating-src.tar.gz.sha)]
+
+

Users will download the mirrored release artifacts from machines outside Apache control. Users need to verify that the copy downloaded is identical to the original. Mirrored copies of checksums, KEYS and signature files (.asc and .md5 files) will be present on the mirrors but must never be used for verification. So, all links from the podling website to signatures, sums and KEYS need to refer to the original documents on www.apache.org. See release signing guide for more information.
+

+
Archiving
+ All Apache releases form an important part of the history of a project. They are therefore archived with the aim of preserving them indefinitely for future reference. All artifacts within www.apache.org/dist will be automatically archived to http://archive.apache.org/dist. When a new artifact is uploaded, it will be sync'd to the archive. The sync'ing is scheduled to operate several times a day. So it may be some hours before an added artifact is archived. When an (archived) artifact is deleted from the live distribution, it will remain in the archives.
+ Please remember that these archives are served from Apache bandwidth. Anyone who wants to obtain a large quantity of data from the archives should contact the Infrastructure Team.
+
+
+
Publishing Maven Artifacts
+ ODF Toolkit chooses to distribute approved releases through the central Maven repository. Please follow this guide:Publishing Maven Artifacts to finish this work.
+ It's clear and simple enough, so I don't need to copy it here.
+
+
+
Publish Document
+ Publish all of the prepared document on the website and update the download page.
+
+
+
Send Announcements
+ The release manager need to send announcements to odf-user and odf-dev lists. Note, announcements should be sent from your @apache.org e-mail address. The sample looks like:
+
+

Subject:[ANNOUNCEMENT] Apache ODF Toolkit(Incubating) 0.5-incubating Release
+ To: odf-users@incubator.apache.org
+ Hi all,
+

The Apache ODF Toolkit(Incubating) team is pleased to announce the release of 0.5-incubating. This is our first Apache release.
+

The Apache ODF Toolkit is a set of Java modules that allow programmatic creation, scanning and manipulation of Open Document Format (ISO/IEC 26300 == ODF) documents. Unlike other approaches which rely on runtime manipulation of heavy-weight editors via an automation interface, the ODF Toolkit is lightweight and ideal for server use.
+

A full list of changes is available in the change log1. People interested should also follow the mail list2 to track progress.
+

The ODF Toolkit source release as well as the pre-built binary deployment packages are listed in the downloads page3. Pre-built versions of all ODF Toolkit components are available in the central Maven repository under Group ID "org.apache.odftoolkit" and Version "0.5-incubating".
+

[1] http://www.apache.org/dist/incubator/odftoolkit/CHANGES-0.5-incubating.txt.
+ [2] http://incubator.apache.org/odftoolkit/mailing-lists.html.
+ [3] http://incubator.apache.org/odftoolkit/downloads.html
+

References

A Guide To Release Management During Incubation (DRAFT)
+
Apache Release Management
+
POI Release Guide
+
POI Release Checklist
+

+ +

Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

+ + Added: websites/staging/ctakes/trunk/content/ctakes/downloads.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/downloads.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/downloads.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,51 @@ + + + + Downloads + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

The Apache cTAKES team is pleased to announce the release of ctakes-0.0.1-incubating soon. This will be our first Apache release.

+ +

Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

+ + Added: websites/staging/ctakes/trunk/content/ctakes/get-involved.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/get-involved.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/get-involved.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,81 @@ + + + + Get Involved + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

You don't need to be a software developer to contribute to +Apache cTAKES. To be successful this project +requires a range of different skills, levels of involvement and degrees of +technical expertise. So, if you want to get involved in Apache cTAKES, there +is almost certainly a role for you.

We are looking for people to:

provide feedback
write or update documentation
help new users
recommend the project to others
test the code and report bugs
fix bugs
give us feedback on required features
write and update the software
create artwork
anything you can see that needs doing

All of these contributions help to keep a project active and strengthen +the community. The project team and the broader community will +therefore welcome and encourage participation, and attempt to make it +as easy as possible for people to get involved.

Mailing lists

Your first engagement with the project should be to subscribe to our mailing lists.

Decision Making

The most important thing about engaging with any Apache project is that everyone +is equal. All people with an opinion are entitled to express that opinion and, where +appropriate, have it considered by the community.

To some the idea of having to establish consensus in a large and distributed team +sounds inefficient and frustrating. Don't despair though, The Apache Way has a +set of simple processes to ensure things proceed at a good pace.

+ +

Copyright © 2011 The Apache Software Foundation, Licensed under the Apache License, Version 2.0.
Apache and the Apache feather logo are trademarks of The Apache Software Foundation.

+ + Added: websites/staging/ctakes/trunk/content/ctakes/license.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/license.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/license.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,226 @@ + + + + + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

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:

+
You must give any other recipients of the Work or Derivative Works a +copy of this License; and
+
+
You must cause any modified files to carry prominent notices stating +that You changed the files; and
+
+
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
+
+
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.
+

+ +

+ + Added: websites/staging/ctakes/trunk/content/ctakes/mailing-lists.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/mailing-lists.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/mailing-lists.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,89 @@ + + + + Mailing Lists + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

cTAKES Mailing Lists

We welcome you to join our mailing lists and let us know about your thoughts or +ideas about Apache cTAKES

Development Mailing List

This is where the community hangs out. This list is used to coordinate +activities and ensure we are all pulling in the same direction. This is a high traffic list, with an average of 57 posts/day.

Subscribe: ctakes-dev-subscribe@incubator.apache.org
Post (after subscription): ctakes-dev@incubator.apache.org
Unsubscribe: ctakes-dev-unsubscribe@incubator.apache.org
Archives
- Markmail
- Apache
+

Commits Mailing List

This is where the community receives automated notifications of any changes to the +cTAKES code and documentation. This is a moderate traffic list, with an average of 10 posts/day.

Subscribe: ctakes-commits-subscribe@incubator.apache.org
Unsubscribe: odf-commmits-unsubscribe@incubator.apache.org
Archives
- Markmail
- Apache
+

Users Mailing List

This is where the users ask questions, suggest features, etc. This is a low traffic list.

Subscribe: ctakes-users-subscribe@incubator.apache.org
Unsubscribe: ctakes-users-unsubscribe@incubator.apache.org
Archives
- Markmail
- Apache
+

+ +

+ + Added: websites/staging/ctakes/trunk/content/ctakes/people.html ============================================================================== --- websites/staging/ctakes/trunk/content/ctakes/people.html (added) +++ websites/staging/ctakes/trunk/content/ctakes/people.html Fri Jul 13 20:04:42 2012 @@ -0,0 +1,89 @@ + + + + Some of our contributors + + + + + + + + + + + + + + +

+ +

Home » Ctakes

+ +

Apache cTAKES is a community developed project. The list below +is a partial list of contributors to the project, for a complete list you'd have +to look at all contributors to our issue tracker, mailing list and version control.

+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +

Apache ID	Name	Home	Skills/Interests
	Guergana K. Savova	Boston, MA, USA
	Sean Finan	Boston, MA, USA
chenpei	Pei Chen	Boston, MA, USA	Java, NLP, ML
james-masanz	James Masanz	MN, USA

+ +