...

The versioned, release tarballs contain no SCM information.  They are intended for use with whatever SCM you select in your custom environment.  The versioned released releases are also available within the NuttX GIT repository clones or forks.  Older releasse releases used tags to identify releases.  For example, the tag nuttx-8.2 would identify the nuttx-8.2 release and a versioned branch could be created with the git command:

git checkout -b newbranch v1.0<branch-name> nuttx-8.2

REVISIT: We do not yet know the form of releases for future Apache releases.  These will most likely already be on a branch.

...

How To Submit Changes For Review

REVISIT: How does this differ from "By GitHub Pull Request(PR)" and "By Emailing a Patch"

Criteria For Acceptance

This section defines what sorts of things committers will examine and verify before allowing changes into NuttX.

...