Another week, another upstream bug

cherry-picked remote crash-fix from upstream

Bugfix release 1.2.1

Proud to tag version 1.2 with lots of features

Feature release including FlexTrans.

Bugfix update for the v1.1 series.

New version 1.1.0

The choice for this number has been discussed and this seems the most
practical by far.
At first we wanted to follow the Core releases, but they have different
core-values and push out hundreds of lines of new code in a bugfix release
which feels dirty to have to inherit.  The result of that is that this
feature release with the soft fork code from Bitcoin Core has received
a bigger feature bumb.  And when that disconnect between versions started
it also stopped making sense to stay close to versioning of Core.
It was time to review the numbering scheme altogether.

Using a less than 1.0 version was a practice that open source has used
for many years. A result of the "Release early, release often" stance.
If memory serves me well, when I talked about this over beers with
Erik S Raymond he explained it such;
The idea was that when the app reaches the set of features required
for the user with the lowest demands to use it for its intended usage,
thats when you call it 1.0.

Bottom line, Bitcoin is certainly far past its 1.0 release, so I marked
the first Classic release as 1.0 and then this release is Classic 1.1.0

Bugfix release

Bitcoin Classic version 0.12.0

Release candidate 1 for release based on Core 0.12.0