Hi,
Will Collect 1.2.1 and Briefcase 1.2.1 work with Aggregate 1.3?
I have users who cannot upgrade Collect and Briefcase yet - will they be
able to use Aggregate 1.3 without problems if I upgrade the server?
There is no problem with Publishers (not used in production yet).
Best regards,
Paul.
Hi Chris,
That is good news - thanks very much for responding so quickly.
Best regards,
Paul.
Paul, as far as I know there are no incompatibilities. We often use older
Collects and older Briefcases with newer Aggregates. The Aggregate team
generally works very hard to remain compatible with existing tools.
Best,
Chris
Hi,
Will Collect 1.2.1 and Briefcase 1.2.1 work with Aggregate 1.3?
I have users who cannot upgrade Collect and Briefcase yet - will they be
able to use Aggregate 1.3 without problems if I upgrade the server?
There is no problem with Publishers (not used in production yet).Best regards,
Paul.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Thanks Mitch - that is very clear now.
Best regards,
Paul.
Yes, we are generally forward and backward compatible w.r.t. interactions
among the various tools (ODK Collect 1.6 will work with Aggregate 1.3, ODK
Briefcase 1.2 will work with both, etc.); this is because the directory
structures and/or communications protocol has been specified for these
interactions and are not in flux.
You should always read the release notes (
http://code.google.com/p/opendatakit/w/list ) and ask if you are unclear.
Our version designations are somewhat confounded because we try to have
major (the "1" in "1.3.2") and minor (the "3" in "1.3.2") numbers in sync
across the platform offerings.
Major revisions (changes to the "1" of "1.3.2") indicate either significant
new functionality (e.g., the 2.0 toolset) or that there may be incompatible
changes that prevent forward migration to the tool -- fortunately, we
haven't needed to do that yet.
Minor revisions (the "3" of "1.3.2") indicate changes that may require
manual steps during migration of that tool from earlier releases. In this
case, the move to 1.3 was triggered by changes within Aggregate. i.e.,
Aggregate 1.2 -> 1.3 -- change to use OAuth2 for publishing into Google
Spreadsheets and Fusion Tables, which broke existing publishers.
Incremental revisions (the "2" of "1.3.2") indicate notable changes, bug
fixes, or additions that do not require any migration steps.
Hi Chris,
That is good news - thanks very much for responding so quickly.
Best regards,
Paul.
On Friday, May 17, 2013 5:00:06 PM UTC+1, Paul wrote:
Hi,
Will Collect 1.2.1 and Briefcase 1.2.1 work with Aggregate 1.3?
I have users who cannot upgrade Collect and Briefcase yet - will they be
able to use Aggregate 1.3 without problems if I upgrade the server?
There is no problem with Publishers (not used in production yet).Best regards,
Paul.
--
You received this message because you are subscribed to the Google Groups
"ODK Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to opendatakit-developers+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
Mitch Sundt
Software Engineer
University of Washington
mitchellsundt@gmail.com