commit | 11ec96ab8a9fbcd2890526b3a2df08a93c97bf55 | [log] [tgz] |
---|---|---|
author | Jonas Termansen <sortie@google.com> | Mon Nov 13 13:27:24 2023 +0000 |
committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Mon Nov 13 13:27:24 2023 +0000 |
tree | eccf56e5a75c078b2d43240b833a1701413daaa5 | |
parent | 6b5b3cc98a23afb58ffdaebf37941aed257ce885 [diff] |
Rename be channel to main. **This change cannot easily be reverted**: After reverting this change, dart-ci-internal-release-bucket-breakglass must be broken by a member of Dart EngProd and gs://dart-archive/channels/main/raw/latest must be purged as well as gs://dartlang-api-docs/channels/main/latest.txt. This operation would risk our release security and it is strongly preferred if any problems can be fixed forward instead. This change will upload the main channel builds to the main directory in the dart-archive bucket instead of the be directory. The existing builds remain where they are and the last version on the be channel remains permanently frozen. The downstream uses already have forward compatibility for the new channel name. The Dart recipes respect the input channel name and output to the release location by that name. The api.dart.dev service will notice when the main channel pops into existence and switch api.dart.dev/be to become api.dart.dev/main. The setup-dart github action will likewise notice when the main channel starts existing. The main channel is not an officially supported product since the builds are not signed and tested and we don't advertise the existence of these builds to our users. Ideally nobody would be broken by this change since they shouldn't be using the main channel builds, but if they are, they will have to rename the channel in their download links. This change ensures that all the release branches and release channels have the same matching names, which simplifies our infrastructure and makes our releases easier to understand. Fixes: b/270022416 Change-Id: Ib47ae7d2ded5fe0d405b3f19c34981c38082a090 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/327940 Commit-Queue: Jonas Termansen <sortie@google.com> Reviewed-by: Alexander Thomas <athom@google.com>
Dart is:
Optimized for UI: Develop with a programming language specialized around the needs of user interface creation.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app.
Fast on all platforms: Compile to ARM & x64 machine code for mobile, desktop, and backend. Or compile to JavaScript for the web.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents on our wiki.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.