...
- As a clone or fork from a NuttX GIT repository, or
- As a versioned , release in the form of a GZIP'ed tarball
The versioned , release tarballs contain no SCM information. They are intended for use with whatever SCM you select in your custom environment.
The code on which versioned releases are based is also available within the NuttX GIT repository clones or forks. Older releases used tags to identify releases Historical releases are identified with tags. For example, the tag nuttx-8.2 would identify identifies the nuttx-8.2 release and a . A versioned branch could be created with the git command:
git checkout -b <branch-name> nuttx-8.2
REVISIT: Are there any differences between the tagged release in GIT and the contents of a release tarball?
REVISIT: We do not yet know the form of releases for future Apache releases. These will most likely already be on a branch. (Note: The release process should be discussed in a different section, or even a completely separate document.)
NuttX GIT Repositories
The Apache NuttX project uses Git SCM as its version control system.
...
Released Code Tarballs
REVISIT: We do not know the form or location of future Apache NuttX releases.
TODOREVISIT: This "Overview" section makes no mention of the buildroot, tools, and uclibc repositories!. We do not yet know how/where those will be hosted.
Creating and Submitting Improvements
...
- The build system
- Tools
- Architectural support
- Board support
- Scheduler
- System calls
- Libraries
TODOREVISIT: This section is incomplete! Please leave the bulletpoints above as-is, and develop the text in new subheadings below.
...