So, from my point of view, we'd be ready to prepare our first incubating release :-)

Mentors?

On 12/03/13 19:19, Sebastian Schaffert wrote:
Hi all,

I think I now finished the release tasks in Maven (MARMOTTA-131). The
distribution consists of the following artifacts:
- the full source code (apache-marmotta-x.x.x-src.[zip|tar.gz]
- the webapp (apache-marmotta-x.x.x-webapp.[zip|tar.gz]
- the installer (apache-marmotta-x.x.x-installer.[zip|tar.gz]

If we later decide that we want to have additional distribution archives
(e.g. for ldclient or ldpath), this is comparably easy to create through
the Maven assembly plugin).

When configuring the distribution tasks, I was copying a bit from
Jackrabbit and from Maven itself. As a result, the distribution task will
automatically create a mail template for starting the release vote :)

To try out how the release would work, you can use the following command:

mvn deploy -Pinstaller,marmotta-release,dist-local -DskipTests=true

This will currently:
- deploy all Maven artifacts into a local repository at /tmp/repo (for
testing if the layout is correct)
- create in target/x.x.x all distribution files that need to be added to
dist.apache.org

For releasing the distribution in real life, there is no need to provide
the profiles on command line. I configured the Maven release plugin to take
care of it.

Anything more that is needed regarding this issue?

Greetings,

Sebastian


2013/3/8 Sebastian Schaffert<[email protected]>


The release of Marmotta is a bit different from both, Jena and Stanbol:
- there is a common release number over all artifacts (different to
Stanbol, easier maintenance)
- the primary means of release is the Maven repository
- there are two binary "launchers" we would like to release in addition: a
.war file and a izPack installer that bundles also Tomcat
- there are a number of libraries that are worth releasing separately as
libraries (Maven and download):
   * ldclient as a Linked Data Client library
   * ldcache as a Linked Data Caching library (builds on ldclient)
   * ldpath as a RDF/Linked Data Query Language (builds on Jena or Sesame,
can use ldcache)
   * kiwi as a RDBMS-based Sesame backend with some advanced functionality
(reasoning, versioning, transactions)
- there is a common source release consisting of the combined source code

The open task here is to create the distribution configuration in the
Maven build, I'll open an issue (MARMOTTA-131).



--
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at

Reply via email to