You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@marmotta.apache.org by Sergio Fernández <se...@salzburgresearch.at> on 2013/03/08 11:45:16 UTC
Re: marmotta meetings
Hi,
what about having a project meeting on IRC next Monday, March 11, around
10.00 CET to discuss the pending things for releasing 3.0.0-incubating?
Thanks!
Cheers,
--
Sergio Fernández
Salzburg Research
+43 662 2288 318
Jakob-Haringer Strasse 5/II
A-5020 Salzburg (Austria)
http://www.salzburgresearch.at
Re: release preparation (was Re: marmotta meetings)
Posted by Sergio Fernández <wi...@apache.org>.
there is light at the end of the tunnel... http://goo.gl/EMF3l :-)
On 13/03/13 10:23, Sergio Fernández wrote:
> 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<se...@gmail.com>
>>
>>>
>>> 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
release preparation (was Re: marmotta meetings)
Posted by Sergio Fernández <se...@salzburgresearch.at>.
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<se...@gmail.com>
>
>>
>> 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
Re: marmotta meetings
Posted by Sebastian Schaffert <ss...@apache.org>.
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 <se...@gmail.com>
>
> 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).
>
Re: marmotta meetings
Posted by Andy Seaborne <an...@apache.org>.
On 08/03/13 15:41, Sergio Fernández wrote:
> Hi,
>
> On 08/03/13 16:24, Andy Seaborne wrote:
>> We gave up on maven at that point - the dist/ area is built with a shell
>> script to control the layout and exactly which files go in.
>
> Custom script per project or something standard for all Apache projects?
It's Jena's script.
There are some standard patterns in projects but also minor differences
in many ways by the time the detail of requirements of each project are
factored in.
> I'll take a look how you do it in Jena.
>
>> I noticed that some headers in files are still (c). POMs especially.
>
> Particularly POMs: I need to check why the maven-license-plugin does not
> cover those files.
>
> What else did you detected?
Generally, it looks pretty good. My original msg was more about the
time it takes and doing after everything else is ready leads to a longer
release cycle. Sometimes things that need discussion or specific
checkign come oup, which means it not just a "doing" task.
I haven't been systematic in looking at the state of the git repo.
On a quick wander though the tree:
NOTICE.txt has "@@TODO@@" :-)
The import of jsonld-java needs handling.
Some of the test materials are different copyright/license (drop a
specific NOTICE/LICENSE files in the directory, maybe a README, so
anyone going straight there finds them)
platform/marmotta-sparql/src/test/resources/test-suite-archive
>
> Andy, tanks for all your support!
NP - it's the mentors job to get you through what is one of the most
important thing about an Apache release - the quality of all the
non-technical aspects.
Working code? That's taken for granted!
Andy
>
> Cheers,
>
Re: marmotta meetings
Posted by Sergio Fernández <wi...@apache.org>.
Hi,
On 08/03/13 16:24, Andy Seaborne wrote:
> We gave up on maven at that point - the dist/ area is built with a shell
> script to control the layout and exactly which files go in.
Custom script per project or something standard for all Apache projects?
I'll take a look how you do it in Jena.
> I noticed that some headers in files are still (c). POMs especially.
Particularly POMs: I need to check why the maven-license-plugin does not
cover those files.
What else did you detected?
Andy, tanks for all your support!
Cheers,
--
Sergio Fernández
Re: marmotta meetings
Posted by Andy Seaborne <an...@apache.org>.
On 08/03/13 15:04, Sebastian Schaffert wrote:
> - there is a common source release consisting of the combined source code
Then it is one release. Multiple binaries don't affect that (Jena is
two binaries, one sourec-release, and flotilla of maven artifacts).
> The open task here is to create the distribution configuration in the Maven
> build, I'll open an issue (MARMOTTA-131).
We gave up on maven at that point - the dist/ area is built with a shell
script to control the layout and exactly which files go in.
We use a bianries and source/ split, and we don't include .asc.md5 and
.asc.sha1 files. We include HEADER.html for suggesting using the mirror
sites.
> Are you aware of any other issues we need to address before the first
> release? We'd like to proceed as quickly with it as possible so that
> projects depending on the old LMF can upgrade to Marmotta.
I noticed that some headers in files are still (c). POMs especially.
Dry-running the whole process is also a good idea ... and deciding who
will be the release manager (and documenting the process). All normal
stuff for setting up really.
Andy
Re: marmotta meetings
Posted by Sebastian Schaffert <se...@gmail.com>.
Hi Andy and all,
thanks for the reminder. Actually we have been looking quite a lot how
other projects solve similar issues. In the last week we have sorted out
the following issues:
- removed all dependencies to code with incompatible licenses (according to
the Apache website):
* c3p0 replaced by Tomcat JDBC Pool
* unboundldap replaced by Apache LDAP
* rdfa-core-java replaced by Semargl RDFa parser
* mysql dependency made optional and added a README.mysql to explain the
situation
- removed all dependencies to code not on Maven Central or Apache
Repositories
* ROME source code integrated into rss parser (under src/ext/java)
* JSON-LD parser source code integrated into JSON-LD parser module (under
src/ext/java)
We have written/extended some Maven plugins that properly list the licenses
and repositories where dependency come from. All other dependencies seem to
be under compatible licenses. The outstanding task is here to update the
NOTICE file to list all dependencies that are under compatible license but
require notice according to Apache policy.
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).
Are you aware of any other issues we need to address before the first
release? We'd like to proceed as quickly with it as possible so that
projects depending on the old LMF can upgrade to Marmotta. :-)
Greetings,
Sebastian
2013/3/8 Andy Seaborne <an...@apache.org>
> Hi,
>>>
>>> what about having a project meeting on IRC next Monday, March 11, around
>>> 10.00 CET to discuss the pending things for releasing 3.0.0-incubating?
>>>
>>
> Gentel reminder :-) might be worth factoring in that time sorting out the
> release process is usually needed; legal, dist/ area, ...
> checkingchecking. This typically ends up on the critical path from
> incubator projects I've seen because the process goes "do code, think about
> release process" (we all techies here!)
>
> Much of it is a one-time task - once done, any subsequent releases are a
> matter of checking the license headers (run the RAT) and only if there are
> new dependencies, or new code not contributed to ASF, is there any work to
> do.
>
> Looking at other projects do is very useful.
>
> The formal release is a source archive or source archives.
> Is it one thing being released or many? (Jena is one, Stanbol is many -
> you can tell by counting the source-release files).
>
> What else are you planning on releasing? maven artifacts and/or a
> download binary?
>
> Andy
>
>
Re: marmotta meetings
Posted by Andy Seaborne <an...@apache.org>.
>> Hi,
>>
>> what about having a project meeting on IRC next Monday, March 11, around
>> 10.00 CET to discuss the pending things for releasing 3.0.0-incubating?
Gentel reminder :-) might be worth factoring in that time sorting out
the release process is usually needed; legal, dist/ area, ...
checkingchecking. This typically ends up on the critical path from
incubator projects I've seen because the process goes "do code, think
about release process" (we all techies here!)
Much of it is a one-time task - once done, any subsequent releases are a
matter of checking the license headers (run the RAT) and only if there
are new dependencies, or new code not contributed to ASF, is there any
work to do.
Looking at other projects do is very useful.
The formal release is a source archive or source archives.
Is it one thing being released or many? (Jena is one, Stanbol is many -
you can tell by counting the source-release files).
What else are you planning on releasing? maven artifacts and/or a
download binary?
Andy
Re: marmotta meetings
Posted by Andy Seaborne <an...@apache.org>.
>> Hi,
>>
>> what about having a project meeting on IRC next Monday, March 11, around
>> 10.00 CET to discuss the pending things for releasing 3.0.0-incubating?
Gentel reminder :-) might be worth factoring in that time sorting out
the release process is usually needed; legal, dist/ area, ...
checkingchecking. This typically ends up on the critical path from
incubator projects I've seen because the process goes "do code, think
about release process" (we all techies here!)
Much of it is a one-time task - once done, any subsequent releases are a
matter of checking the license headers (run the RAT) and only if there
are new dependencies, or new code not contributed to ASF, is there any
work to do.
Looking at other projects do is very useful.
The formal release is a source archive or source archives.
Is it one thing being released or many? (Jena is one, Stanbol is many -
you can tell by counting the source-release files).
What else are you planning on releasing? maven artifacts and/or a
download binary?
Andy
Re: marmotta meetings
Posted by Sergio Fernández <wi...@apache.org>.
so... irc now?
On 08/03/13 11:47, Sebastian Schaffert wrote:
> +1
>
>
> 2013/3/8 Sergio Fernández<se...@salzburgresearch.at>
>
>> Hi,
>>
>> what about having a project meeting on IRC next Monday, March 11, around
>> 10.00 CET to discuss the pending things for releasing 3.0.0-incubating?
>>
>> Thanks!
>>
>> Cheers,
>>
>> --
>> Sergio Fernández
>> Salzburg Research
>> +43 662 2288 318
>> Jakob-Haringer Strasse 5/II
>> A-5020 Salzburg (Austria)
>> http://www.salzburgresearch.at
>>
>
--
Sergio Fernández
Re: marmotta meetings
Posted by Sebastian Schaffert <se...@gmail.com>.
+1
2013/3/8 Sergio Fernández <se...@salzburgresearch.at>
> Hi,
>
> what about having a project meeting on IRC next Monday, March 11, around
> 10.00 CET to discuss the pending things for releasing 3.0.0-incubating?
>
> Thanks!
>
> Cheers,
>
> --
> Sergio Fernández
> Salzburg Research
> +43 662 2288 318
> Jakob-Haringer Strasse 5/II
> A-5020 Salzburg (Austria)
> http://www.salzburgresearch.at
>