Skip to content
This repository has been archived by the owner on Jan 28, 2024. It is now read-only.

New feature language development

Jump to bottom
Daco Harkes edited this page Apr 6, 2022 · 1 revision

When working on large features (or new languages) we would like to have the following things in place:

  1. Be able to review work in progress (to avoid getting 10.000 LOC PRs).
  2. Run continuous integration on our test suite.

At the same time we would like the master branch to be in a state in which we can always release:

  1. Not give the impression that work in progress APIs will be there the next release.

We could work with feature branches, but that complicates:

  1. Running continuous integration for all features.
  2. Merging refactorings back in to feature branches.

So, instead, we opt to merge everything to the master branch and document the features / languages that are work in progress in two ways:

  1. We print a severe warning in the console whenever such feature is used.
  2. The public API documentation contains "EXPERIMENTAL" (including the README.md on the yaml keys).
Clone this wiki locally