Hi Gab, In meantime I could run a local release build without having problems. I have checked META-INF info of the local JARs/WARs and the info files containing references. I did not find issues.
To your question about the NOTICE I do not have really an opinion. Finally I would rate the RC with +1 Regards, Stephan -----Original Message----- From: Gabriele Columbro [mailto:[email protected]] Sent: Mittwoch, 1. September 2010 17:32 To: [email protected] Subject: Validation of release packages (was: Fwd: [jira] Commented: (CMIS-224) Improve legal/standard aspects of the release process / packaging) Hey guys, finally today I could dedicate myself to improve the legal / distribution aspects of the release. As per the issue below, AFAIU the packaging issues blocking 0.1.0-rc1 should have been covered. So, before engaging the release process (also as we're waiting on [1]), I'd like to ask you guys to have a look the commodity (/dist) packages I deployed at [1], and help me confirm or deny that: 1. All JARs/WARs have correct info in META-INF (latest SNAPSHOT at [2] or you can build from trunk) 2. All commodity packages I uploaded at [3] have correct LICENSE and DISCLAIMER info, and DEPENDENCIES and NOTICE that instead refer to contained WAR/JAR specific DEPENDENCIES and NOTICE. Docs has not DEPS and NOTICE, as there are not shipped deps. Minor glitch, not blocker I believe: the source-release package, being generated by ASF POM inherited settings is listing superPOM project deps in DEPENDENCIES and NOTICE. One question to conclude: referring to Nick's comments at [4], do you think we should have anything else in NOTICE for all packages? In other words, which of the licenses mentioned in the various DEPENDENCIES files actually require a NOTICE? If you guys are happy with the packages, I'll close CMIS-224 and we can move on with the release. Hope this helps! Gab [1] https://issues.apache.org/jira/browse/CMIS-247 [2] https://repository.apache.org/content/repositories/snapshots/org/apache/chemistry/ [3] http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-SNAPSHOT/release/ [4] http://www.mail-archive.com/[email protected]/msg24953.html Begin forwarded message: > From: "Gabriele Columbro (JIRA)" <[email protected]> > Date: September 1, 2010 4:15:53 PM GMT+02:00 > To: [email protected] > Subject: [jira] Commented: (CMIS-224) Improve legal/standard aspects > of the release process / packaging > > > [ > https://issues.apache.org/jira/browse/CMIS-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12905030 > > #action_12905030 ] > > Gabriele Columbro commented on CMIS-224: > ---------------------------------------- > > r 991541 should resolve issues at > http://www.mail-archive.com/[email protected]/msg24955.html > : > > Now: > 1. all JARs and WARs have now information in META-INF > 2. supplemental models are augmented...hopefully everything is in (i > did not check every single JAR, any volounteer?) > 3. for the commodity packages (zip/tar.gz), as they are mere > aggregation of project JARs/WARs, I created dummy DEPENDENCIES/ > NOTICE files which instruct the user to look in the META-INF of the > opencmis J2EE artifact > > > Sample commodity packages can be found at: > > http://people.apache.org/~gabriele/chemistry/opencmis/0.1.0-incubating-SNAPSHOT/release/ > > If the list (and especially the menthors) give us green light with > these packages, I'll close the issue and start the release process. > >> Improve legal/standard aspects of the release process / packaging >> ----------------------------------------------------------------- >> >> Key: CMIS-224 >> URL: https://issues.apache.org/jira/browse/CMIS-224 >> Project: Chemistry >> Issue Type: Task >> Components: build&release >> Affects Versions: 0.1.0-incubating >> Reporter: Gabriele Columbro >> Assignee: Gabriele Columbro >> Priority: Minor >> Fix For: 0.2.0-incubating >> >> Original Estimate: 4h >> Remaining Estimate: 4h >> >> As per ML thread >> http://mail-archives.apache.org/mod_mbox/incubator-chemistry-dev/201006.mbox/%[email protected]%3e >> >> , >> there are some legal aspects of the release process which need QA >> before be fully compliant with the ASF legal policies. >> Specifically: >> - Publish a list of dependencies with their applicable license. >> Especially required for "category b" type of deps >> (http://www.apache.org/legal/resolved.html#category-b >> ) , like JAX-WS RI, mimepull and saaj >> - add LICENSE and NOTICE also in WARs (and not only in JARs) >> - cleanup SVN EOL >> - add missing license headers > > -- > This message is automatically generated by JIRA. > - > You can reply to this email to add a comment to the issue online. > -- Gabriele Columbro Alfresco Software, Ltd. http://www.mindthegab.com http://twitter.com/mindthegabz " Keyboard not found. Press F1 to continue. "
