Add notes about how branch status will be documented across releases. (#69)

docs/How/release_process.md

@@ -24,6 +24,23 @@ The below diagram illustrates the life-cycle of a single branch and indicates th
     
     This is why we strongly discourage forking Project Mu for direct modification (ie. consumption, not contribution). Instead, leverage the distributed repo management system and override management system to integrate proprietary code/modules.
 
+## Current Branch Status
+
+While the earliest release branches may not be included in this process, starting with `release/201903` and going forwards the status of each branch will be recorded in the README.rst file at the root of the branch. In general, the README found in Basecore will contain information that is common to all of the Mu submodules, but each submodule will also have its own README for each release branch that contains notes specific to the development that occurs in that submodule during a release cycle.
+
+The README will also contain a summary of the branch status at a given time. For example, here is a sample status for Basecore `release/201903` as of the time of this writing:
+
+```text
+Current Phase:
+  Development
+
+Entered Current Phase:
+  2019/03/25
+
+Planned Exit Date:
+  May 2019
+```
+
 ## Upstream Integration Phase
 
 At this time, we are targeting upstream integrations for roughly once a quarter, attempting to align 1:1 with the TianoCore stable release cadence. Prior to an integration, the status dashboard (not yet created) will be updated with the target date of completion and the target TianoCore commit and/or release. For example, a plan was made to transition off of `release/20180529` when TianoCore announced the `edk2-stable201808` release.