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 <[email protected]> > 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 > >
