* Retire changelog entries mechanism
It is no longer used these days, so it simply imposes unnecessary
work. If it ever becomes useful again, retrieving the relevant
scripts from history should be relatively easy.
* Remove references to `unreleased.sh`
* Re-add `unreleased.sh` for summarization -- feedback from @mziolekda`
Coordinating the full stable release process now happens in a
single place, for which I added a link. Release testing coordination
is now handled by a single person, with clearly defined responsibilities
and handover of tasks.
changelog_begin
changelog_end
Specifically, try to slightly reorganize it in terms of what people are
trying to achieve, rather than what type of release they ultimatly need
to create.
CHANGELOG_BEGIN
CHANGELOG_END
Turns out splitting the file (#13160) was not such a good idea.
Also tweak the text a little bit, hopefully making it clearer.
CHANGELOG_BEGIN
CHANGELOG_END
In docs:
* doc that we require Java 11, not 8
In release instructions:
* mention everywhere that all-lowercase party entries should be made
* wrong line number for variable go-to-defn check
CHANGELOG_BEGIN
CHANGELOG_END
I suppose whoever fixed this forgot to update these instructions, but as of `2.0.0-snapshot.20220204.9165.0.225c58f4` I observed well-formed "Bob" and "Alice" values in the messaging dropdowns.
The issue with the message dropdown looking like garbage will
obviously be fixed. Just trying to reflect the current state.
changelog_begin
changelog_end
This could not be achieved previously due to an issue that has
been fixed by https://github.com/DACH-NY/canton/pull/8475.
The next release should be tested again with the Canton-based
sandbox to ensure it works on both Windows and MacOS/Linux.
changelog_begin
changelog_end
The Canton sandbox currently has a startup issue that
has to be fixed that causes an unusually long startup
time on Windows that ends up triggering a timeout.
Can be reverted once https://github.com/DACH-NY/canton/issues/8331
is fixed.
changelog_begin
changelog_end
* Make quickstart-java template work with canton
Also update the quickstart-java release test instructions to use the new sandbox. This is a bit more involved than before, because of the party names being different every time, but I hope this is not too much of a burden. The test here is similar to what gets tested in the assistant integration test for quickstart-java.
changelog_begin
changelog_end
* try to fix indentation
And change the relevant release test instructions to make it clear this
isn't a quickstart-java project, but a project that uses the default
template (skeleton).
changelog_begin
changelog_end
Was a bit too eager in the last PR, and changed the release test to use
`daml start` instead of `daml start --sandbox-kv`. This PR reverts this
until we make create-daml-app work with the new sandbox.
changelog_begin
changelog_end
* Change default sandbox to canton.
Some progress on #11831
* made `daml start` use canton sandbox by default
* changed the non-ledger api ports to use free ports by default
(still haven't tried using port 0 instead of `getFreePort`).
* renamed `daml sandbox-canton` to `daml sandbox`
* implement a `--static-time` option for `daml sandbox` that sets the
canton clock type parameter to `sim-clock`
* moved the quickstart-java integration test to use the new sandbox
* the test uses `--static-time`, but doesn't really depend on it
changelog_begin
changelog_end
* fix parens
* fix hot reload test
* reinstant --sandbox-kv in create-daml-app test for now
* fix damlStart test
NodeJS 12 is eol in April and there are already packages (e.g. vsce)
that dropped support. We probably should upgrade even further but for
now I’m going with the most conservative approach.
changelog_begin
changelog_end
* Rename daml sandbox to daml sandbox-kv
Also drop the default sandbox on `daml start`
Part of #11831
changelog_begin
changelog_end
* update release test instructions
* try to fix a couple compat tests
* dont need special 0.0.0 logic
* buildifier-fixx
1. Correct link for the releases page
2. Move Windows up because I thought I was done with Windows after the
create-daml-app test and I killed my machine.
CHANGELOG_BEGIN
CHANGELOG_END
* Replace many occurrences of DAML with Daml
* Update docs logo
* A few more CLI occurrences
CHANGELOG_BEGIN
- Change DAML capitalization and docs logo
CHANGELOG_END
* Fix some over-eager replacements
* A few mor occurrences in md files
* Address comments in *.proto files
* Change case in comments and strings in .ts files
* Revert changes to frozen proto files
* Also revert LF 1.11
* Update get-daml.sh
* Update windows installer
* Include .py files
* Include comments in .daml files
* More instances in the assistant CLI
* some more help texts
As we strive for more inclusiveness, we are becoming less comfortable
with historically-charged terms being used in our everyday work.
This is targeted for merge on Dec 26, _after_ the necessary
corresponding changes at both the GitHub and Azure Pipelines levels.
CHANGELOG_BEGIN
- DAML Connect development is now conducted from the `main` branch,
rather than the `master` one. If you had any dependency on the
digital-asset/daml repository, you will need to update this parameter.
CHANGELOG_END
* Update release instructions to follow newest GSG
We've lately integrated the codegens into `daml start`, which made the GSG significantly shorter in turn. Reflect these changes in the release instructions. Also reword some parts where I found the instructions ambiguous on first reading.
CHANGELOG_BEGIN
CHANGELOG_END
* Apply suggestions
CHANGELOG_BEGIN
CHANGELOG_END
- Followup to #7338, adjusting release test instructions for changes to the Java
quickstart, mismatches found testing #7462. Compare to
docs/source/app-dev/bindings-java/quickstart/template-root/daml/Main.daml for line #
references.
CHANGELOG_BEGIN
CHANGELOG_END
