>> new properties like "is_robot" (or "is_crawler", etc.?) are new as of >>DeviceMap
Sure, if you can make that change, that would be helpful. Otherwise I can do it. Speaking of which, can we also add some new devices? Im pretty sure new phones got released recently. Might be a good idea to try and get them in there. Ideas on how we can do this? There must be a blog or something tracking new phone releases??? >> Could we also include "test_data" I dont have any use for it, nor do I know of anything consuming this data. So im not planning on supporting it or releasing it. If there is a good use case, then im open to hearing it. >> Whether the improvements of the "new" client really make 1.1.0 Yes, this is definitely a 1.1 release. Some new features were added. In particular, a new option Device object response, JSON output, and a few other minor touches. >> when could we also start deploying something to Apache Maven repo Good question, still need to research what needs to be done here. Maybe after we graduate? Not sure. It might be as simple as getting our distribution releases promoted... maybe? >> they often maintain 2 or more sets of either clients I will not be maintaining the legacy ODDR client. I spent a lot of time mucking around that codebase and it isn't something I want to use or support. There are numerous issues with this client. You are more than welcome to release and support it. Since no code has been committed to it here, it looks like the last commit to it over 2 years ago to the day: https://github.com/OpenDDRdotORG/OpenDDR-Java/commits/master ________________________________ From: Werner Keil <[email protected]> To: "[email protected]" <[email protected]>; Reza <[email protected]> Sent: Monday, August 4, 2014 4:25 PM Subject: Re: next client and data release I'd point out in the vocabulary, that new properties like "is_robot" (or "is_crawler", etc.?) are new as of DeviceMap, not squeeze them in the middle of existing ODDR ones. Other than that, if the clients work well, I see no problem with a 1.0.1 data release relatively soon. Could we also include "test_data" or is there a problem with that? Whether the improvements of the "new" client really make 1.1.0 I can't say (has the "1.0.x" bugfix release been used??) but as e.g. Browsermap is trailing a bit there is also not anything tragic in 1.1 vs. 1.0.1. To allow further changes to the data file, 1.0.1 feels better. It depends on the classpath fix in data 1.0.1, thus I would prepare a release of the W3C DDR library as soon as the new data is released. Especially for data, when could we also start deploying something to Apache Maven repo? As discusssed, the 2 clients don't directly compete, and see some of the big vendors (DeviceAtlas or DetectRight, etc. not so much WURFL) they often maintain 2 or more sets of either clients, data sets of both. So a W3C compatible library can make it easier for their existing codebase to migrate if they wish (e.g. commercial libraries where the vendor no longer exists like Volantis) As soon as the data structure was to change, we'll see, if the W3C aspects remain, then it won't be an issue, or if the "client.next" may be the only one for a new "2.x" data files... Cheers, Werner On Mon, Aug 4, 2014 at 10:12 PM, Reza <[email protected]> wrote: What is a good date for our next data release (1.0.1) and client release (1.1.0)? > >Other than what has already been discussed and put into JIRA, are there any >other features or improvements wanted in these releases?
