Release only an "offline" installer.

[Paul Hargrove]

This issue is split off from issue #214.

Here are the three comments in the "thread" being moved here:

Paul Hargrove

I would like to propose an alternative resolution to this issue in the upcoming 2019.9.0 release.
I want us to consider making the "offline" installer the default (and possibly only) download.
Such a change would have its own benefits, but in relation to this issue it would render SSL negotiation a moot point for anyone not setting GASNET to an https URL.
Reactions?

Dan Bonachea

I would like to propose an alternative resolution to this issue in the upcoming 2019.9.0 release. I want us to consider making the "offline" installer the default (and possibly only) download.

I agree we should transition to the offline installer being the only tarball we package for the upcoming release. We'll need to discuss further what file naming convention to use moving forward.
However, the code implementing the online installer needs to remain functional and supported, as that's the mode users get when git cloning the public repo. This notably includes any users asked to validate bug fixes in the develop branch.

Assuming we resolve to follow-though with this plan, this issue can be downgraded in priority and/or closed as "won't fix".

Paul Hargrove

I am fine with a "won't fix" resolution on this issue, so long as we open a new one to cover the transition to offline installer as the only tarball. I will take care of that later today, or perhaps tomorrow, unless somebody beats me to it.

[Paul Hargrove]

This will require updates to (at least) our documentation, release procedure, and to utils/release.sh

[Dan Bonachea]

Proposed solution in pull request #112

[Dan Bonachea]

issue #250: update release-builder script

Now generate only the offline tarball

Fixes issue #250

→ <<cset eabce5c9da53>>