[FB] Moving Buck to a stable/development branch publication model

Created by: gnuthor

In order to allow us to experiment on fundamental changes to the core of Buck, future changes made by Facebook’s Build Infra team to the Buck code base will be published to a development branch. The current master branch is moving to a stable role that doesn’t automatically get these changes.

For this stable master branch we will continue to merge PRs and help with issue tickets as we do now, we are also open to pulling interesting commits from the dev branch on demand.

We will make sure that changes to the new dev branch continue to pass Buck’s test suites inside FB’s internal CI system while we change features and APIs, potentially breaking backwards compatibility. Our goal is to be able to put the buck dev code base into a state that allows easier reuse and evolution of interesting parts quickly without putting non-FB users of buck at risk that might be dependent on some of these code paths.

Longer term this ability to move fast and experiment will lead to a vastly improved build experience. We're exploring changes that will make for a more dynamic, more incremental, and much, much faster build system. We will clearly separate the core from the language rules providing the community a more stable API to depend on.

The Facebook Build Infra Team