Members present: wastl, westei, jfrank, wikier ---------------- Meeting summary: ----------------
1. Preface a. http://maven.apache.org/pom/asf/ (wastl, 1) IRC log follows: # 1. Preface # 09:14:26 [wikier]: so, topics? 09:14:36 [wikier]: I mean, apart of the open issues for releasing 09:15:05 [wastl]: that is for me the main topic 09:15:19 [wastl]: what is still blocking the release 09:16:26 [wikier]: afaik, not legal issues 09:16:36 [wikier]: we'd just need to refect at the notice the code that has been imported 09:16:42 [wikier]: and manage the headers properly 09:17:49 [wastl]: ok, so two tasks still open: 09:17:49 [wastl]: - check all headers 09:17:56 [wastl]: - update NOTICE file 09:18:28 [wastl]: and then the issues on the list, mainly: 09:18:41 [wastl]: - create distribution tasks in build process 09:19:27 [wastl]: I can take care of the distribution tasks 09:19:50 [wastl]: I anyways documented the different kinds of release already in the build file 09:19:59 [wastl]: and there are certainly Maven plugins for it 09:21:11 [wikier]: there is a profile at the apache parent pom 09:21:19 [wikier]: but jena guys are using a custom script for it 09:21:21 [wastl]: http://maven.apache.org/plugins/maven-assembly-plugin/ 09:21:49 [wastl]: yes, but I like doing everything in maven, it is less effort in the future 09:22:19 [wastl]: how are releases uploaded to the Apache download server, btw? 09:22:19 [wikier]: ++1 09:22:51 [wikier]: I'd like to avoid os-dependent script when possible 09:23:12 [wikier]: and in this case should be possible 09:23:50 [wastl]: yes, actually you are right, it is already in the parent pom 09:24:05 [wikier]: ok, if wastl takes care of the distribution tasks, I can take care of the legal ones, where jfrank had already done an extensive checking 09:24:21 [wikier]: -Papache-release, I thing is its name 09:24:22 [jfrank]: the settings in apache-parent are also valid for incubation? 09:24:28 [wikier]: should be 09:24:36 [wikier]: the rules are the same 09:24:38 [wikier]: so... 09:25:12 [jfrank]: the rules, but also the target? (repos/dist/release/marmotta) 09:25:19 [wastl]: just out of curiousity, I am trying to build with the apache-release profile 09:25:20 [wastl]: yes 09:25:29 [wastl]: everything in an incubating project is the same 09:25:41 [wastl]: except the version number has to carry -incubating 09:25:49 [wikier]: umm 09:25:51 [wikier]: so, two exceptions 09:26:04 [wikier]: - target should be repos/dist/release/incubator/marmotta ? 09:26:19 [wikier]: - version with the suffix -incubating 09:26:56 [jfrank]: https://dist.apache.org/repos/dist/release/incubator/ 09:27:26 [wikier]: so we may need to overrite those concrete settings 09:27:27 [wastl]: ok, so this is for uploading the release assemblies? 09:27:36 [wikier]: see how other incubator project does ;-) 09:27:57 [jfrank]: that's the official release. 09:28:07 [wikier]: bloodhound should be a good example, since they are graduating this month :-) 09:28:20 [jfrank]: but first, we have to pass all votes 09:28:27 [wikier]: aja, staging release where? 09:28:36 [jfrank]: afaik wherever we want. 09:28:49 [wikier]: https://dist.apache.org/repos/dist/dev/ 09:28:57 [jfrank]: no 09:29:04 [wikier]: yes, there 09:29:04 [wikier]: https://dist.apache.org/repos/dist/dev/incubator/ 09:29:41 [jfrank]: dist/dev is for snapshot, etc... releases 09:30:04 [wastl]: well for bloodhound dev does not contain snapshots 09:30:12 [jfrank]: they also need a vote first 09:30:22 [wikier]: http://incubator.apache.org/ctakes/ctakes-release-guide.html 09:30:42 [wikier]: no, should be a final release 09:30:52 [wikier]: to voted, first by the project, them by the IPMC 09:30:57 [wikier]: and then moved to dist 09:31:12 [jfrank]: so i understand the docs 09:31:36 [wikier]: http://helix.incubator.apache.org/releasing.html 09:31:50 [wikier]: those two projects have good documentation about the process 09:32:26 [wikier]: see point 5 of helix 09:34:26 [wikier]: maybe we'd need to document the process at the same time 09:35:27 [wastl]: yes, and ours will look a bit different 09:35:35 [wastl]: I'd like to do a binary release as well 09:36:04 [wastl]: btw, the wikier-foaf test fails 09:36:43 [wastl]: sometimes 09:38:42 [wastl]: funny, it fails always on command line but works in intellij 09:39:57 [wikier]: sometimes? 09:40:11 [wikier]: if it fails, should be because timeout 09:40:19 [wikier]: direct raw file 09:40:20 [wikier]: which was not tested 09:40:35 [wikier]: but it is the easiest thing to test 09:40:41 [wastl]: no, it was more complicated, but fixed 09:40:51 [wastl]: the problem is you are using non-ASCII characters in the sparql file 09:40:56 [wikier]: ok, I'll see the diff 09:40:58 [wastl]: IntelliJ by default uses UTF-8 09:41:07 [wastl]: command line uses system encoding 09:41:26 [wikier]: exactly that was one of the purpose of the test: test language and encoding 09:41:28 [wikier]: aja 09:41:34 [wikier]: that's why it never fails to be 09:41:42 [wikier]: linux uses utf-8 by default 09:41:57 [wikier]: ACTION wonders why other os don't 09:42:20 [wikier]: back to the release 09:42:28 [wikier]: wastl: the release is just a code release 09:42:35 [wastl]: ACTION still running the release build 09:42:57 [wikier]: binaries (maven artifacts and launchers) are not for voting, but of course useful for users 09:42:59 [wastl]: wikier: yes I know, but on the other hand, the page http://incubator.apache.org/guides/releasemanagement.html says 09:43:42 [wastl]: Most users interact with a project only through its releases. They are a public face of the project and are often the first chance to make a good impression. 09:44:05 [wastl]: so it would be nice to also distribute binary releases like many other apache projects do 09:44:27 [wastl]: at least a war 09:45:04 [wikier]: both war and installer 09:45:11 [wikier]: ok 09:45:11 [wikier]: fine 09:45:34 [wikier]: conclusion: code + maven artifact + launchers 09:45:41 [jfrank]: but the vote is on the code only 09:46:04 [wastl]: yes 09:46:04 [wastl]: exactly 09:46:11 [westei]: IMO binary releases are important. Its already an issue in Stanbol that we have no binary releases 09:46:13 [wastl]: that's what I understood 09:46:19 [westei]: yes 09:46:26 [westei]: vote is on the source release 09:46:44 [wastl]: so I will update the build for the apache-release profile so it creates: 09:46:49 [wastl]: - source assembly 09:46:56 [wastl]: - war file distribution 09:47:04 [wastl]: - installer distribution 09:48:19 [wastl]: ok, build finished 09:48:34 [wastl]: by default it simply creates a .zip file with all the source 09:49:04 [wastl]: funny thing is that it creates NOTICE, LICENSE and README automatically 09:49:05 [wastl]: so we have them twice 09:49:14 [jfrank]: check the content 09:49:19 [wastl]: ah, not the README 09:49:27 [wastl]: only NOTICE and LICENSE and DEPENDENCIES 09:49:41 [wastl]: NOTICE: 09:49:49 [wastl]: Apache Marmotta 09:49:49 [wastl]: Copyright 2012-2013 The Apache Software Foundation 09:49:49 [wastl]: 09:49:49 [jfrank]: that's part of the maven-remote-...-plugin 09:49:49 [wastl]: This product includes software developed at 09:49:49 [wastl]: The Apache Software Foundation (http://www.apache.org/). 09:50:11 [wastl]: LICENSE contains the apache license 09:50:41 [wastl]: DEPENDENCIES: 09:50:41 [wastl]: // ------------------------------------------------------------------ 09:50:41 [wastl]: // Transitive dependencies of this project determined from the 09:50:41 [wastl]: // maven pom organized by organization. 09:50:42 [wastl]: // ------------------------------------------------------------------ 09:50:49 [wastl]: 09:50:49 [wastl]: Apache Marmotta 09:50:56 [wastl]: nothing more 09:51:11 [wastl]: so we'll need to look how these are generated 09:51:26 [wikier]: umm, notices too? 09:51:26 [jfrank]: http://maven.apache.org/plugins/maven-remote-resources-plugin/ 09:51:34 [wastl]: maybe it is not necessary to have our own NOTICE file then, we can maybe provide the input so it is generated 09:51:41 [wikier]: for us is a bit comples, since notice should also include reference to many js libs 09:51:51 [wikier]: aja 09:53:49 [wastl]: but this should be possible nonetheless 09:53:56 [wastl]: they are using apparently assembly descriptors 09:54:49 [wastl]: I will have a look in a free minute 09:55:22 [jfrank]: try renaming NOTICE.txt to NOTICE... 09:56:41 [wastl]: I am looking for the documentation of the apache parent POM 09:56:49 [wastl]: apparently it can generate a site 09:57:11 [wastl]: in the worst case I check out the parent pom source code and build it here 10:02:11 [wastl]: ok, this is important: 10:02:13 [wastl]: #link http://maven.apache.org/pom/asf/ 10:04:26 [wastl]: I have to leave now, next meeting 10:04:26 [wastl]: cu
