The release notes https://code.google.com/p/opendatakit/wiki/SurveyReleaseNotes help to see
what has been worked on recently, but knowing which components are likely
to receive attention in coming months would be a big help to those of us
wanting to migrate to 2.0, for making more informed decisions.
···
On Tuesday, 30 June 2015 16:20:53 UTC+2, Andrew wrote:
>
> Hi ODK team,
>
> Just wondering if you have a more up to date roadmap for planned
> development than this one (2012)
> .
>
> The release notes
> help to
> see what has been worked on recently, but knowing which components are
> likely to receive attention in coming months would be a big help to those
> of us wanting to migrate to 2.0, for making more informed decisions.
>
> Thanks, keep up the good work!
> Andrew
>
We've decided to NOT release a June/July release; we are focusing on some
build system changes (migrating off of googlecode, to gradle, to Android
Studio from Eclipse, and expanding our testing).
We are also investigating alternatives for the AppDesigner in an effort to
simplify the set-up for that environment. These may impact the internals of
Survey or Tables, and we wanted to stabilize those before pushing out a new
release.
···
=====================
ODK Collect
The next ODK Collect will have an OpenStreetMap integration and a wide
range of new translations.
======================
ODK Aggregate
The next ODK Aggregate will have changes to the installer to support the
'module' architecture and remove our use of 'backends'. The install/upload
script may also change to require a manual step to get an access key.
The release notes https://code.google.com/p/opendatakit/wiki/SurveyReleaseNotes help to
see what has been worked on recently, but knowing which components are
likely to receive attention in coming months would be a big help to those
of us wanting to migrate to 2.0, for making more informed decisions.
Migrating ODK code bases from Google Code & Eclipse & Maven to GitHub &
Android Studio & Gradle (as well as other software package switches). This
is long overdue maintenance step that will take weeks.
Replacing JQuery Mobile with Bootstrap to speed up page transitions and
improve other annoyances users have reported
Isolating DB access to a single Android service
A major restructuring of the files on the Android device.
Increasing code reuse between the Android apps and the apps running on
a PC
Our priority is to produce software that "just works" and is usable by a
variety of organizations. To achieve this goal it often requires a slow
iterative feedback loop. I would like to thank the people who braved the
alphas and the betas to give us the valuable feedback that we are
incorporating into the next round of changes. It makes the tools better for
everyone.
The next release target is a beta release in September(ish). Based on the
feedback from the beta we hope to target a full release candidate for early
2016. However, as always the development team is small and there is a lot
on our plate. For example incompatible changes to Android or other common
OSes sometimes causes work on ODK 2.0 tools to stop to bring ODK 1.0 tools
up to date. The ODK core team does not give precise dates we only tell you
what we are thinking as we plan the next month or two.
Waylon
···
On Tue, Jun 30, 2015 at 10:16 AM, Mitch Sundt wrote:
We've decided to NOT release a June/July release; we are focusing on some
build system changes (migrating off of googlecode, to gradle, to Android
Studio from Eclipse, and expanding our testing).
We are also investigating alternatives for the AppDesigner in an effort to
simplify the set-up for that environment. These may impact the internals of
Survey or Tables, and we wanted to stabilize those before pushing out a new
release.
=====================
ODK Collect
The next ODK Collect will have an OpenStreetMap integration and a wide
range of new translations.
======================
ODK Aggregate
The next ODK Aggregate will have changes to the installer to support the
'module' architecture and remove our use of 'backends'. The install/upload
script may also change to require a manual step to get an access key.
The release notes https://code.google.com/p/opendatakit/wiki/SurveyReleaseNotes help to
see what has been worked on recently, but knowing which components are
likely to receive attention in coming months would be a big help to those
of us wanting to migrate to 2.0, for making more informed decisions.
Great, thanks Mitch and Waylon, appreciate the detailed feedback.
Regards,
Andrew
···
On Saturday, 4 July 2015 01:42:50 UTC+2, Waylon Brunette wrote:
>
>
> The ODK core team is currently focusing on incorporating feedback from
> people who have experimented with rev124 and rev126 (as Mitch pointed to
> the last email projection is being delayed by a couple of months
> https://groups.google.com/forum/#!msg/opendatakit-developers/S6zuUmDQ4Sk/lLweT5Z7vmsJ
> ).
>
> To reiterate some of the major changes are:
> 1) Migrating ODK code bases from Google Code & Eclipse & Maven to GitHub
> & Android Studio & Gradle (as well as other software package switches).
> This is long overdue maintenance step that will take weeks.
> 2) Replacing JQuery Mobile with Bootstrap to speed up page transitions
> and improve other annoyances users have reported
> 3) Isolating DB access to a single Android service
> 4) A major restructuring of the files on the Android device.
> 5) Increasing code reuse between the Android apps and the apps running on
> a PC
>
> Our priority is to produce software that "just works" and is usable by a
> variety of organizations. To achieve this goal it often requires a slow
> iterative feedback loop. I would like to thank the people who braved the
> alphas and the betas to give us the valuable feedback that we are
> incorporating into the next round of changes. It makes the tools better for
> everyone.
>
> The next release target is a beta release in September(ish). Based on the
> feedback from the beta we hope to target a full release candidate for early
> 2016. However, as always the development team is small and there is a lot
> on our plate. For example incompatible changes to Android or other common
> OSes sometimes causes work on ODK 2.0 tools to stop to bring ODK 1.0 tools
> up to date. The ODK core team does not give precise dates we only tell you
> what we are thinking as we plan the next month or two.
>
> Waylon
>
> On Tue, Jun 30, 2015 at 10:16 AM, Mitch Sundt <mitche...@gmail.com > wrote:
>
>> This e-mail has an overview of the upcoming ODK 2.0 changes:
>> https://groups.google.com/d/msg/opendatakit-developers/S6zuUmDQ4Sk/lLweT5Z7vmsJ
>>
>> We've decided to NOT release a June/July release; we are focusing on some
>> build system changes (migrating off of googlecode, to gradle, to Android
>> Studio from Eclipse, and expanding our testing).
>>
>> We are also investigating alternatives for the AppDesigner in an effort
>> to simplify the set-up for that environment. These may impact the internals
>> of Survey or Tables, and we wanted to stabilize those before pushing out a
>> new release.
>>
>> =====================
>> ODK Collect
>>
>> The next ODK Collect will have an OpenStreetMap integration and a wide
>> range of new translations.
>>
>> ======================
>> ODK Aggregate
>>
>> The next ODK Aggregate will have changes to the installer to support the
>> 'module' architecture and remove our use of 'backends'. The install/upload
>> script may also change to require a manual step to get an access key.
>>
>> ----------------
>> Mitch
>>
>> On Tue, Jun 30, 2015 at 7:22 AM, Andrew <acawo...@gmail.com wrote:
>>
>>> Sorry, I meant the change logs
>>> , not
>>> the release notes.
>>>
>>>
>>>
>>> On Tuesday, 30 June 2015 16:20:53 UTC+2, Andrew wrote:
>>>>
>>>> Hi ODK team,
>>>>
>>>> Just wondering if you have a more up to date roadmap for planned
>>>> development than this one (2012)
>>>> .
>>>>
>>>> The release notes
>>>> help
>>>> to see what has been worked on recently, but knowing which components are
>>>> likely to receive attention in coming months would be a big help to those
>>>> of us wanting to migrate to 2.0, for making more informed decisions.
>>>>
>>>> Thanks, keep up the good work!
>>>> Andrew
>>>>
>>> --
>>> --
>>> Post: opend...@googlegroups.com
>>> Unsubscribe: opendatakit...@googlegroups.com
>>> Options: http://groups.google.com/group/opendatakit?hl=en
>>>
>>> ---
>>> You received this message because you are subscribed to the Google
>>> Groups "ODK Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to opendatakit...@googlegroups.com .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Mitch Sundt
>> Software Engineer
>> University of Washington
>> mitche...@gmail.com
>>
>> --
>> --
>> Post: opend...@googlegroups.com
>> Unsubscribe: opendatakit...@googlegroups.com
>> Options: http://groups.google.com/group/opendatakit?hl=en
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "ODK Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to opendatakit...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>