[roll] Roll fuchsia [rfc] Amend RFC-0103 to provide rationale.

RFC-103 defined the situations in which SWD changes will require an RFC.
During recent discussion of an in-work SWD RFC it became clear that the
rationale for requiring an RFC was not clear in some of these,
specifically the meaning and cost of a stepping stone release was not
clear to some readers.

This ammendment adds a short justification for each of the situations in
which a SWD RFC is required.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/685372
Original-Revision: 66dde16801c268f995ff6a6572fcaf1c6aded80f
GitOrigin-RevId: 7c1cff81bed2bd96eba2663eb102360a5eaad7ac
Change-Id: I19da9b857f3d3c0a4b2b210217ce30499de8eb6b
1 file changed
tree: a59092579aa5e199379e90929dd4dabfe70c2cc9
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.