I thought we plan to do that now, or do you mean a "1.0" one?[?] AFAIR I dropped the "0.9.9" in favor of a simple "0.9-SNAPSHOT" leaving a bit more room towards a 1.0 release.
On Thu, Jul 3, 2014 at 7:08 PM, Reza <[email protected]> wrote: > Right now its at 0.9. So I will stick with that until we do our first > release. > > > ________________________________ > From: Werner Keil <[email protected]> > To: "[email protected]" < > [email protected]>; Reza <[email protected]> > Sent: Thursday, July 3, 2014 12:47 PM > Subject: Re: Challenge #2: make a release > > > > Great. Did you see what the recommended version number is for each of the > packages? > > Eclipse or JCP Standards often start with 1.x as soon as a project is > final or graduates. > Especially the device data (not tags, those sometimes reflect the OpenDDR > source of updates) version was "0.99" until recently, if we were to raise > that to "1.0" it could increase later. > Not sure about the API, there the last time I got all Maven projects to a > coordinated build those were in the 0.2 region. If as Bertrand suggested it > could be "Alpha" or "Beta", too in order to graduate, then I am not sure > about jumping to 1.0 there. For the data artifact, please let's pick > something we feel is appropriate > > Werner > > > > > On Thu, Jul 3, 2014 at 6:40 PM, Reza <[email protected]> > wrote: > > I tried replying to this on my apache account and it never made it thru. > > > >Yes, data and api will be separate packages. > > > >I last worked on changes so the java api can load the devicemap-data > directly from a jar in the classpath. So all you need to do is include the > devicemap-data dependency in your pom. The java api also has the ability to > load the data over URL too. I just need to clean up the api a bit so its > clear how to use each loading method. Once its all cleaned up, it should be > a very simple process to get this all up and running. I will email the > final packages and build instructions to the group when its ready, > hopefully this weekend. > > > > > > > >________________________________ > > From: eberhard speer jr. <[email protected]> > >To: "[email protected]" < > [email protected]> > >Sent: Thursday, July 3, 2014 12:34 PM > >Subject: Re: Challenge #2: make a release > > > > > > > >-----BEGIN PGP SIGNED MESSAGE----- > >Hash: SHA1 > > > >Hi, > > > >Regarding Werner's question on including the data in the release : > > > >I would suggest a separate 'package' for the data, so that all > >versions can refer to the same data package and the data [higher > >frequency I would image] and code releases each have a 'standard > >channel' and can release as required independently or coordinated. > > > >esjr > >-----BEGIN PGP SIGNATURE----- > >Version: GnuPG v1.4.8 (MingW32) > >Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > > >iQEcBAEBAgAGBQJTtYYiAAoJEOxywXcFLKYcLHwIAIgUALGbBul+jsEoP/BQwzpg > >9rku83B4PK2V3pUBDfMTk2cfWwKZZkgmDfNJshbQBGRuEmbgHW9dJItqz7lm36Zo > >SKYUzXYRSWS1opUyIIafSABDF6Ew8tfS+vXw7IZQikvNFxS+LxaQfTgMJBlDE/tz > >qxcwq/kEN4m6CHcQ0Ds1C/gPPXFYkNA4vpy3nlezvBnRFIThbOydBejZf0weqZ3w > >IYZQPVRATqIrYOgYEcFkRnAmPjR+yisO8CqHC3F4di2ybY7i4LWTUkJXIqYBGqJC > >Cx+hkqQV1qQOUt4Ayv9+TNOkVnfOuJF8TicPgzZSGXny2ZDzzUokV/MnOp2qikw= > >=xVc2 > >-----END PGP SIGNATURE----- >
