New release v1.2.0

[holgerd77]

No description provided.

[s1na]

On second thought, seems to me that doing a release with only place-holder values for the HF can be somewhat confusing. I wonder if we can for example use ethereumjs-common's master branch (with the merged #51) for testing and release 1.2.0 with full Istanbul release? Or do you see a strong case for doing the release now and working towards a complete support in multiple minor releases?

[holgerd77]

@s1na I think we'll likely run into caching problems if we just use master. I would also like to release draft Istanbul libraries early on for experimentation, since the final Istanbul version is still months away, and in the official library releases I wouldn't want to use master Common version as dependency.

So I still have a strong tendency to do these as official releases. The Common library is just used by us anyhow.

[s1na]

As pointed out by @holgerd77, this library is mostly used internally, and the changelog clearly states that this is only draft support for Istanbul.

Let the great Istanbul HF integration begin 😄