Thanks for preparing the release! Using 0.1.0 style version also on the commons-rdf-api would probably simplify a lot for the release plugin.. specially when/if we were to try to do the equivalent of a 0.1.1 release of commons-rdf-simple. It would also be more in line with semantic versioning to always have 3 digits - even if we don't intend to publish a .1 patch of the -api. (Any .1 patch of the API would be just textual formatting changes of javadoc?)
I guess you would bump master to be on 0.1.1-SNAPSHOT afterwards, or are you setting them to 0.2-SNAPSHOT and 0.2.0-SNAPSHOT? On 6 May 2015 at 12:23, Sergio Fernández <[email protected]> wrote: > Just because I have it fresh, I want to share some notes abuut the > preparation of our first release. > > Basically I followed the regular process described at > http://www.apache.org/dev/release-publishing.html using the > maven-release-plugin: > > mvn release:clean > mvn release:prepare > mvn release:perform -DconnectionUrl=scm:git:file://`pwd`/.git > git push > git push --tags > > The versioning schema agreed is not well supported by the > maven-release-plugin. so I needed to manually fix the api versions by > amending the local commits before performing the release. We should find a > better approach > > The commons-parent causes some troubles, not only for us: > https://github.com/apache/commons-vfs/blob/trunk/pom.xml#L538 I tried all, > but it keeps generating a > commons-rdf-parent-x.y.z-incubating-source-release.zip including wrong > things (e.g., examples). > > And that's more or less all behind the scenes. > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 > e: [email protected] > w: http://redlink.co -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/0000-0001-9842-9718
