Upgrading Aggregate Directly From v1.4.15 to v1.7.0 on GAE

What is the problem? Please be detailed.

I've reviewed the general steps for upgrading Aggregate several times, but I want to be sure that I'm not missing something.

The instructions state: "Do not simply upgrade from an old version of Aggregate to the latest version. It is important to upgrade sequentially through versions, instead of trying to upgrade directly to the latest version from an older one."

However, based on my review of the release notes, it looks like I should be able to upgrade directly from v1.4.15 to v1.7.0. The only issue I can see is down on the upgrade notes for v1.4.13 there is a mention of needing to enable Google Sheets API if publishing to Google Sheets.

Could some from the wonderful ODK development team let me know if I'm on the right track (or straighten me out if not)?

What ODK tool and version are you using? And on what device and operating system version?

Aggregate v1.4.15

What steps can we take to reproduce the problem?

What you have you tried to fix the problem?

Anything else we should know or have? If you have a test form or screenshots or logs, attach here.

Hi,

You may have missed the paragraph on that documentation as the following: "Do not simply upgrade from an old version of Aggregate to the latest version. It is important to upgrade sequentially through versions, instead of trying to upgrade directly to the latest version from an older one."

I believe, you need to upgrade step by step.

Thanks

We recommend you upgrade step by step because it's guaranteed to be safe. Upgrading from v1.4.15 to v1.70 is probably fine, but if we can't guarantee safety, we don't recommend it.

If you are a gambler, at least make sure you have a good backup of Aggregate in place.

Clarification: Only upgrade to the production versions, not the betas. So you'd go from v1.4.15 to v1.5.0 to v1.6.1 to v1.7.latest.

1 Like

@A.N.M_AL-IMRAN thanks for the quick reply! Indeed, this sentence that you highlight is the reason for my post.

@yanokwa I like the safe route! Sorry for the follow-up question, but to be sure, between v1.4.15 and v1.7.0 there are:

  • v1.5.0-beta.0
  • v1.5.0
  • v1.6.0-beta.0
  • v1.6.0
  • v1.6.1
  • v1.7.0-beta.0
  • v1.7.0

Can we skip the beta versions and/or the changes in the third digit (e.g. v1.6.0 to v1.6.1) with a path like:

  • v1.5.x
  • v1.6.x
  • v1.7.x

or would it be best to go through all six?

2 Likes

Do not install the betas. Use the newest of each production release. So 1.5.latest, 1.6.latest, etc

Okay, thanks @yanokwa, this is super helpful.