As W3C DDR relies on 1.0.1 data, I see no reason against releasing that rather soon.
Looking at Sling (@Bertrand, do you know, if delivery to at least the Apache Maven Snapshot repo happens from Jenkins?) there is another aspect we should not forget after an update to data and the libraries using it. Apache Sling Health Check Samples 1.0.6 (September 5th, 2014) Was just out today (the Sling page also contains news a bit more frequently;-D) So a collection of at least Java examples currently in SVN would also be great to release every now and then. If it isn't in Maven, I'll probably adjust the master POM, all example modules included in their parent POM currently build fine, so they should also work on Jenkins. Werner On Fri, Sep 5, 2014 at 2:05 PM, Reza Naghibi <[email protected] > wrote: > Sure, so we can start doing this after our 1.0.1 data release, which will > hopefully be soon. > > I will document the release steps on our wiki the next time we do it. I > agree, it would be nice to have 1 step by step guide for the whole process. > Right now the steps are spread across many documents. > > > > <div>-------- Original message --------</div><div>From: Werner Keil < > [email protected]> </div><div>Date:09/05/2014 7:54 AM (GMT-05:00) > </div><div>To: [email protected] </div><div>Subject: Re: > How to deploy artifacts to Maven Central </div><div> > </div>Sounds good, Device Data 1.0.0 contained a bug regarding the > builders, but > that's why I'm only releasing the W3C compliant implementation after 1.0.1 > with those fixes is also out. Having all data artifacts out allows easier > adjustment of individual projects or apps to the version they prefer via > Maven;-) > > Thanks, > Werner > > On Fri, Sep 5, 2014 at 1:49 PM, Reza Naghibi > <[email protected] > > wrote: > > > Nice, looks very straight forward. If it's ok, I would like to hold on > > publishing our first java client release, 1.0.0, in favor of our next > > client release 1.1.0. Device data should be good to go for all our > released > > versions. > > > > Question... why duplicate the documentation locally for our project? Do > > you want the steps customized to match our project and build environment? > > > > Thanks!! > > > > <div>-------- Original message --------</div><div>From: Bertrand > > Delacretaz <[email protected]> </div><div>Date:09/05/2014 4:45 AM > > (GMT-05:00) </div><div>To: [email protected] > > </div><div>Subject: How to deploy artifacts to Maven Central </div><div> > > </div>Hi, > > > > IIRC there was a question about this a while ago - the info is at > > http://www.apache.org/dev/publishing-maven-artifacts.html > > > > I'm not sure if using the Apache parent pom is required for that, but > > if it is that's > > > > <parent> > > <groupId>org.apache</groupId> > > <artifactId>apache</artifactId> > > <version>14</version> > > </parent> > > > > and once again, it would be very nice if someone could document the > > release steps at http://incubator.apache.org/devicemap/ for future > > releases. > > > http://sling.apache.org/documentation/development/release-management.html > > is a good example of that. > > > > HTH, > > -Bertrand > > >
