Summa SourceForge Administrativia

This page collects everything needed to run the Summa Source Forge project as an admin.

SSH Access

To log in you must be an admin, or be granted shell right from an admin. To log in do

ssh -t USER,summa@shell.sourceforge.net create

This will give you a shell with the working directory set to that of the user. To access the Summa project files do

cd /home/groups/s/su/summa/

Unsurprisingly the web-accesible files are located in the htdocs directory of said path.

Online Javadocs

The online Summa javadocs go to

/home/groups/s/su/summa/htdocs/apidocs/summa/SUMMA_VERSION/

If we ever decide to ship other software bundles under the Summa unbrella (a "contrib" library fx.), docs go to

/home/groups/s/su/summa/htdocs/apidocs/SUB_PROJECT/SUB_PROJECT_VERSION/

SFTP Mount for Web Files

You can set up an SFTP (listed as SSH) mount in Gnome's Nautilus file manager by clicking Places -> Connect to Server.... Set service type to SSH, server to web.sourceforge.net, folder to /home/groups/s/su/summa/htdocs, and user name to $USER,summa. You probably also want to check the "Add bookmark" checkbox. Now you have drag and drop access to the online Summa files.

Making a Release

In your shell run

  export SF_USER=<YOU SOURCEFORGE LOGIN>

and

  export VERSION=<THE NEW SUMMA VERSION>

Make sure that test cases run and that you are happy with trunk as it is
Bump the version in pom.xml and Common/src/dk/statsbiblioteket/summa/common/SummaVersion.java
```
 mvn -N versions:update-child-modules
```
Generate the ChangeLog file (it's recommended to use svn2cl, launched as svn2cl.sh -i -a --break-before-msg=2)
Based on the generated ChangeLog write release notes in the NEWS file

Commit (Remember to commit pom.xml's)

  svn ci build.properties ChangeLog NEWS Common/src/dk/statsbiblioteket/summa/common/SummaConstants.java

Tag the release, eg.

  svn cp https://summa.svn.sourceforge.net/svnroot/summa/trunk https://summa.svn.sourceforge.net/svnroot/summa/tags/summa-$VERSION

Go to a temporary dir or other safe place and do a clean checkout of the newly created tag:
```
  svn co https://summa.svn.sourceforge.net/svnroot/summa/tags/summa-$VERSION
```
Roll the source ZIP file. From just outside the clean tagged checkout do
```
  zip -r summa-src-$VERSION.zip summa-$VERSION -x \*.svn\*
```

Change directory into the tagged checkout and run

  cd summa-$VERSION/Web; ./mkLinks.sh; cd ..; mvn deploy -DskipTests

Update summa.sourceforge.net/doc/ with new API

   mvn javadoc:aggregate
   scp -r target/site/apidocs/ $SF_USER,summa@frs.sourceforge.net:/home/groups/s/su/summa/htdocs/apidocs/summa/$VERSION

Update schema and /home/groups/s/su/summa/htdocs/doc/index.html to point af new summa version

Upload files for the release to the SourceForge File Release System (FRS). This can be done either directly from the SF website, or from the command line. The files to upload are:

ChangeLog
NEWS
Samples/Summix/target/summix-$VERSION.zip
Samples/Assemply/target/summa-standalone-$VERSION.jar
../summa-src-$VERSION.zip

To upload files for $VERSION (eg. "1.4.16") from the command line proceed as follows:

10.1. Create a directory in the FRS:

ssh -t $SF_USER,summa@shell.sourceforge.net create
mkdir /home/frs/project/s/su/summa/releases/$VERSION
shutdown

10.2. Upload the actual files:

Note that the trailing backslash is important!

scp NEWS ChangeLog Samples/Summix/target/summix-$VERSION.zip Samples/Assemply/target/summa-standalone-$VERSION.jar ../summa-src-$VERSION.zip $SF_USER,summa@frs.sourceforge.net:/home/frs/project/s/su/summa/releases/$VERSION/

Change standard download on SF
Send release announcements to the mailing lists summa-devel and summa-announce containing a small intro and the contents of the NEWS file