[snmp/compiler] Release notes, appup and proper version
Merge branch 'bjorn/compiler/float/OTP-10788'

* bjorn/compiler/float/OTP-10788:
  beam_type: Convert integer to float at compile time
  compiler: Use the literal pool for floating point constants
Merge branch 'bjorn/compiler/crash/OTP-10794'

* bjorn/compiler/crash/OTP-10794:
  Test setelement(1, not_a_tuple, NewValue)
  Fix crash in the compiler when compiling element(2, not_a_tuple)
Merge branch 'bjorn/remove-packages/OTP-10348'

* bjorn/remove-packages/OTP-10348:
  kernel docs: Remove references to specs_packages.xml
Update primary bootstrap
Fix unsafe accesses to driver data from win32 fd/vanilla/spawn drivers
Revert "Prepare release"

This reverts commit a0e362765d9d4afb0211f49eb787d2139b3eb7be.
Merge branch 'maint-r15' into maint
Add two tests for unused multiple values in effect context
asn1_SUITE: Mend broken test_modified_x420/1

The test_modified_x420/1 test case had several problems that
prevented it to detect the bugs it was supposed to find:

1) There was a 'catch' at the top-level so that it could never fail.
2) There was a call to the now non-existing ssl_base64 module.
3) It did not test all options for the BER backend.

While at it, also clean way the remaining ?line macros and some
out-commented code.
asn1_erl_nif: Correct broken length encoding

The ber_bin_v2 backend calls a NIF function to decode all tags
and lengths. Even open types that should not be decoded will also be
decoded, which makes it necessary to later re-encode the data using
a NIF function.

The NIF function incorrectly encoded lengths.
[test_server] Don't write unicode strings to latin1 log files

The unicode update of test_server for R16A introduced a few potential
errors when logging to files. Sometimes ~tp or ~ts was used for
formatting also when writing to files that were not opened with the
{encoding,utf8} option. If then the argument contained unicode
characters above 255, the file descriptor would crash. This has been
corrected by the following modifications:

* Since the 'unexpected_io' log file is used only when the test case
  HTML file is not available (e.g. between test cases), this file is
  now also a HTML file and as other test_server HTML logs it is always
  UTF-8 encoded

* Since it is possible to change which information is going to which
  log file (with test_server_ctrl:set_levels/3), we do not have full
  control over which information is written to which file. This means
  that any printout could be written to the 'major' log file
  (suite.log), which was earlier encoded as latin1. To avoid crashing
  this file descriptor due to unicode strings, the 'major' log file is
  now also encoded in UTF-8 (possible incopatibility).

* The cross_cover.info file is no longer a text file which can be read
  with file:consult/1, instead it is written as a pure binary file
  using term_to_binary when writing and binary_to_term when reading.

* The encoding of the file named 'last_name', which only content is
  the path to the last run.<timestamp> directory, is now dependent on
  the file name mode of the VM. If file names are expected to be
  unicode, then the 'last_name' file is UTF-8 encoded, else it is
  latin1 encoded.

Also, ~tp is changed back to ~p unless it is somehow likely that the
argument includes strings. It is not obvious that this is the correct
thing to do, but some decission had to be taken...
Merge branch 'jv/cover-patches/OTP-10778'

* jv/cover-patches/OTP-10778:
  Fix a bug in cover when used with no_auto_import
  Ensure cover keeps the proper file source
  cover now relies on the compile info to find file sources
Fix flush of fd-driver on Windows
Fix erts-5.10 release notes
[snmp/compiler] Added test case for BITS import
[snmp/compiler] MIB compiler did not handle forward index ref

The MIB compiler could not handle a table index refering to
an object defined later in the MIB.
[snmp/compiler] Add the mib (ALARM-MIB)
[snmp/compiler] Proper release nodes
[snmp/compiler] Add test case and test mib