ODK Build Maintenance Outage: Thurs 16 Feb, 23:59 UTC

Hello all:

Build will be down for a scheduled maintenance window tomorrow at 23:59
UTC, which should last for no longer than 90 minutes. We will do our best
to keep it far shorter than that.

Please be sure you wrap up and save your work before then, as once we pull
the plug you will no longer be able to. If you have work you must
absolutely get done during that window, I suggest you take a look at
the desktop
version https://github.com/opendatakit/build/releases of Build.

Why are we taking the service down? Several reasons:
• To apply critical security updates.
• To upgrade the entire site from http:// to https://, with the maximum
amount of available security we can provide for you (HTTPS-only secure
cookies, with Perfect Forward Secrecy).
• To migrate some of our storage infrastructure to a different system,
which should enable us to implement some new features we wouldn't otherwise
be able to, as well as make ODK Build friendlier to new developers trying
to dive in and contribute.
• We are also moving from a New Jersey-based server to an Amsterdam-based
one, which should hopefully improve network latency for many of you.

If you have any questions please feel free to reply to me directly. I will
send out further updates during the outage.

Best,
Clint

The window has begun. Wish me luck. :slight_smile:

··· On Wed, Feb 15, 2017 at 2:41 PM, Clint Tseng wrote:

Hello all:

Build will be down for a scheduled maintenance window tomorrow at 23:59
UTC, which should last for no longer than 90 minutes. We will do our best
to keep it far shorter than that.

Please be sure you wrap up and save your work before then, as once we pull
the plug you will no longer be able to. If you have work you must
absolutely get done during that window, I suggest you take a look at the desktop
version https://github.com/opendatakit/build/releases of Build.

Why are we taking the service down? Several reasons:
• To apply critical security updates.
• To upgrade the entire site from http:// to https://, with the maximum
amount of available security we can provide for you (HTTPS-only secure
cookies, with Perfect Forward Secrecy).
• To migrate some of our storage infrastructure to a different system,
which should enable us to implement some new features we wouldn't otherwise
be able to, as well as make ODK Build friendlier to new developers trying
to dive in and contribute.
• We are also moving from a New Jersey-based server to an Amsterdam-based
one, which should hopefully improve network latency for many of you.

If you have any questions please feel free to reply to me directly. I will
send out further updates during the outage.

Best,
Clint

Maintenance is complete! You'll need to log back in again. Please let me
know if you see anything wrong at all once you do.

Thanks,
Clint

··· On Thu, Feb 16, 2017 at 4:01 PM, Clint Tseng wrote:

The window has begun. Wish me luck. :slight_smile:

On Wed, Feb 15, 2017 at 2:41 PM, Clint Tseng cxlt@cs.washington.edu wrote:

Hello all:

Build will be down for a scheduled maintenance window tomorrow at
23:59 UTC, which should last for no longer than 90 minutes. We will do our
best to keep it far shorter than that.

Please be sure you wrap up and save your work before then, as once we
pull the plug you will no longer be able to. If you have work you must
absolutely get done during that window, I suggest you take a look at the desktop
version https://github.com/opendatakit/build/releases of Build.

Why are we taking the service down? Several reasons:
• To apply critical security updates.
• To upgrade the entire site from http:// to https://, with the maximum
amount of available security we can provide for you (HTTPS-only secure
cookies, with Perfect Forward Secrecy).
• To migrate some of our storage infrastructure to a different system,
which should enable us to implement some new features we wouldn't otherwise
be able to, as well as make ODK Build friendlier to new developers trying
to dive in and contribute.
• We are also moving from a New Jersey-based server to an Amsterdam-based
one, which should hopefully improve network latency for many of you.

If you have any questions please feel free to reply to me directly. I
will send out further updates during the outage.

Best,
Clint