I'm trying to prepare 0.2.0 release candidates locally. I'm following https://commons.apache.org/releases/
I'm using mvn -Prelease release:prepare -DdryRun=true - Commons (and we) use the 'release' profile rather than 'apache-release'. I've removed <finalName> from pom.xml as it caused api/target/ and simple/target to both contain misleading files apache-commons-rdf.jar - the apache- prefix is set correctly through the assembly config anyway - aka target/apache-commons-rdf-0.2.0-incubating-SNAPSHOT-src.tar.gz. I've moved src/main/assembly/src.xml to src/assembly/src.xml to be inline with the newest Commons parent. I've re-enabled tar.gz so that we will release both .zip and .tar.gz, like other Commons projects (see thread http://mail-archives.apache.org/mod_mbox/incubator-commonsrdf-dev/201505.mbox/%3CCAB917RKhrdUtx0coV_4HnMr-vy0atcSXrtkmEvObuDcZkyMD-Q%40mail.gmail.com%3E ) We don't have a RELEASE-NOTES.txt - so I made https://github.com/apache/incubator-commonsrdf/blob/master/RELEASE-NOTES.txt Shall I make retrospective JIRA issues for those changes missing? -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
