StephanErb closed pull request #45: Miscellaneous cosmetic fixes and Travis CI 
badge
URL: https://github.com/apache/aurora/pull/45
 
 
   

This is a PR merged from a forked repository.
As GitHub hides the original diff on merge, it is displayed below for
the sake of provenance:

As this is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
new file mode 100644
index 000000000..16b696fdd
--- /dev/null
+++ b/.github/pull_request_template.md
@@ -0,0 +1,6 @@
+### Description:
+
+
+
+
+### Testing Done:
diff --git a/README.md b/README.md
index ff39a01e6..0d35c5fd8 100644
--- a/README.md
+++ b/README.md
@@ -1,5 +1,7 @@
 ![Aurora Logo](docs/images/aurora_logo.png)
 
+[![Build 
Status](https://travis-ci.org/apache/aurora.svg?branch=master)](https://travis-ci.org/apache/aurora)
+
 [Apache Aurora](https://aurora.apache.org/) lets you use an [Apache 
Mesos](http://mesos.apache.org)
 cluster as a private cloud. It supports running long-running services, cron 
jobs, and ad-hoc jobs.
 Aurora aims to make it extremely quick and easy to take a built application 
and run it on machines
diff --git a/RELEASE-NOTES.md b/RELEASE-NOTES.md
index 4212f1179..7e044a100 100644
--- a/RELEASE-NOTES.md
+++ b/RELEASE-NOTES.md
@@ -6,14 +6,14 @@
   in batches of different sizes. For example, an update which modifies a total 
of 10 instances may
   be done in batch sizes of 2, 3, and 5. The number of updated instances must 
equal the size of the
   current group size in order to move to the next group size. If the number of 
updated instances is
-  greater to the sum of all group sizes, the last group size will be used in 
perpetuity until all 
+  greater to the sum of all group sizes, the last group size will be used in 
perpetuity until all
   instances are updated.
   A new field has been added to `UpdateConfig` called `update_strategy`.
   Update strategy may take a `QueueUpdateStrategy`, `BatchUpdateStrategy`,
   or a `VariableBatchUpdateStrategy` object. `QueueUpdateStrategy` and 
`BatchUpdateStrategy` take
   a single integer argument while `VariableBatchUpdateStrategy` takes a list 
of positive integers
   as an argument.
-  
+
 ### Deprecations and removals:
 
 - Deprecated use of Thrift fields `JobUpdateSettings.waitForBatchCompletion` 
and
@@ -21,7 +21,7 @@
   instead. Note that these same constructs, as represented in the Aurora DSL, 
are still valid
   as they will be converted to the new field automatically by the client
   for backwards compatibility.
-  
+
 0.21.0
 ======
 


 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to