daml/unreleased.rst

26 lines
2.1 KiB
ReStructuredText
Raw Normal View History

2019-08-13 19:23:03 +03:00
.. Copyright (c) 2019 The DAML Authors. All rights reserved.
Move unreleased user-facing features to its own file (#1762) * Move unreleased user-facing features to its own file docs/source/support/release-notes.rst unfortunately represents a "global lock" when it comes to submitting contributions: if another contribution changed it while another was going through the CI/review process, the latter would have to go again through the CI build after resolving the conflict and merging the resulting commit. The contributors originally tried to address this problem by letting the system automatically performing this operation, but this failed because release notes were moved to the wrong section by mistake. This simple change would allow the contributors to let the system take care of merging on its own, because existing release notes will no longer be corrupted by the process. There is a caveat: the automatic merging could result in invalid RST (mostly because of missing newlines). This would push the task of ensuring the release notes are valid RST to the release. I would argue this can be done quite easily and that this is checked automatically when rendering RST to HTML, so it could be a nuisance during release but it would make the day-to-day contributions easier. * Address https://github.com/digital-asset/daml/pull/1762#issuecomment-503540993 * Address https://github.com/digital-asset/daml/pull/1762#pullrequestreview-251676158 * Address https://github.com/digital-asset/daml/pull/1762#discussion_r295279530 * Remove HEAD section from release-notes.rst * Address https://github.com/digital-asset/daml/pull/1762#pullrequestreview-251678791 * Address https://github.com/digital-asset/daml/pull/1762#issuecomment-503549896
2019-06-19 17:32:03 +03:00
.. SPDX-License-Identifier: Apache-2.0
Release notes
#############
This page contains release notes for the SDK.
HEAD — ongoing
--------------
+ [DAML Integration Kit] The reference implementation can now spin up multiple nodes, either scaling
a single participant horizontally or adding new participants. Check the CLI ``--help`` option.
+ [DAML Integration Kit] The test tool now runs the double spend test on a shared contract in a
multi-node setup (as well as single-node).
+ [DAML Standard Library] **BREAKING CHANGE** The ``(/)`` operator was moved out of the ``Fractional`` typeclass into a separate ``Divisible`` typeclass, which is now the parent class of ``Fractional``. The ``Int`` instance of ``Fractional`` is discontinued, but there is an ``Int`` instance of ``Divisible``. This change will break projects that rely on the ``Fractional Int`` instance. To fix that, change the code to rely on ``Divisible Int`` instead. This change will also break projects where a ``Fractional`` instance is defined. To fix that, add a ``Divisible`` instance and move the definition of ``(/)`` there.
+ [DAML Integration Kit] The test tool can now run all semantic test in a multi-node setup.
+ [DAML Assistant] The HTTP JSON API is now integrated with the
assistant and distributed with the SDK. It can either be launched
via ``daml json-api`` or via ``daml start``. You can find more information in the
`README <https://github.com/digital-asset/daml/blob/master/ledger-service/http-json/README.md>`_.
+ [JSON API] **BREAKING CHANGE** The ``/contracts/search`` request payload must use
``"%templates"`` in place of ``"templateIds"`` to select which templates' contracts are
returned. See `issue #2777 <https://github.com/digital-asset/daml/issues/2777>`_.
+ [DAML Compiler] **BREAKING CHANGE** Move the DAML-LF produced by generic template instantiations closer to the surface syntax. See the documentation on `How DAML types are translated to DAML-LF <https://docs.daml.com/app-dev/daml-lf-translation.html#template-types>`__ for details.