summaryrefslogtreecommitdiff
path: root/Documentation
diff options
context:
space:
mode:
authorVance Morrison <vancemorrison@comcast.net>2018-03-18 07:31:17 -0700
committerVance Morrison <vancemorrison@comcast.net>2018-03-18 07:31:17 -0700
commitd27214498a8229cc78bdff80345640435a9e185c (patch)
tree4bdca97315a0c2ae223d96f3b1309fff5cd52388 /Documentation
parentebdc98cf6c19e8a4f2de02e28f51048d25cbf70f (diff)
downloadcoreclr-d27214498a8229cc78bdff80345640435a9e185c.tar.gz
coreclr-d27214498a8229cc78bdff80345640435a9e185c.tar.bz2
coreclr-d27214498a8229cc78bdff80345640435a9e185c.zip
Review feedback
Diffstat (limited to 'Documentation')
-rw-r--r--Documentation/workflow/OfficalAndDailyBuilds.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/Documentation/workflow/OfficalAndDailyBuilds.md b/Documentation/workflow/OfficalAndDailyBuilds.md
index 9ae49d7631..083df3e282 100644
--- a/Documentation/workflow/OfficalAndDailyBuilds.md
+++ b/Documentation/workflow/OfficalAndDailyBuilds.md
@@ -17,9 +17,10 @@ repositories. You can see what is available from
* NETCore.App at <https://dotnet.myget.org/feed/dotnet-core/package/nuget/Microsoft.NETCore.App>
These builds have a version number that follows the the versioning scheme described below (month number/day of month),
-but they also will have a component that indicate which Git Branch the are working from
+but they also will have a component that indicate which Git Branch the are working from (note these names were
+correct as of 1/2018 and may change but the concept of a suffix that designates the branch is likely to persist)
- * preview1 - are daily builds from the 'release/*' branch where * is the next official version to be released
+ * preview1 - are daily builds from the 'release/\*' branch where \* is the next official version to be released
* preview2 - are daily builds from the 'master' branch (where active work happens first (typically))
Thus if your goal is just to get the latest bug fixes and features, you don't need to build CoreCLR yourself you