svn commit: r1641111 - /incubator/slider/site/trunk/content/release_notes/release-0.50.2.md

[el...@apache.org]

Author: elserj
Date: Sat Nov 22 19:20:20 2014
New Revision: 1641111

URL: http://svn.apache.org/r1641111
Log:
SLIDER-544 Stub out release notes for 0.60.0

Modified:
    incubator/slider/site/trunk/content/release_notes/release-0.50.2.md

Modified: incubator/slider/site/trunk/content/release_notes/release-0.50.2.md
URL: http://svn.apache.org/viewvc/incubator/slider/site/trunk/content/release_notes/release-0.50.2.md?rev=1641111&r1=1641110&r2=1641111&view=diff
==============================================================================
--- incubator/slider/site/trunk/content/release_notes/release-0.50.2.md (original)
+++ incubator/slider/site/trunk/content/release_notes/release-0.50.2.md Sat Nov 22 19:20:20 2014
@@ -15,50 +15,22 @@
    limitations under the License.
 -->
   
-# Apache Slider Release 0.50.2 (incubating)
+# Apache Slider Release 0.60.0 (incubating)
 
 August 2014
 
-This release is built against Apache Hadoop 2.4.1, HBase 0.98.4 and Accumulo 1.6.0
+This release is built against Apache Hadoop 2.6.0, HBase 0.98.4 and Accumulo 1.6.1
 
 
 ## Key changes
 
-1. Slider now has an integral Chaos Monkey  [SLIDER-202](https://issues.apache.org/jira/browse/SLIDER-202).
-This can be configured to start through options in `internal.json`; it will kill
-a random container or the AM itself based on configured properties. This is intended
-for use in testing —though may be used in production if desired, and if the 
-application and YARN cluster configured to tolerate the failures.
-
-1. Slider runs on Java 6 [SLIDER-322](https://issues.apache.org/jira/browse/SLIDER-322).
-We plan to keep it Java 6-compatible until Hadoop core upgrades to Java 7.
-
-1. Improved Port allocation and management in component instances.
-([SLIDER-219](https://issues.apache.org/jira/browse/SLIDER-219),
- [SLIDER-273](https://issues.apache.org/jira/browse/SLIDER-273)
+TBD
 
 ## Incompatible Changes
 
-### [SLIDER-77](https://issues.apache.org/jira/browse/SLIDER-77): use a window for tracking container failures.
-
-Previously a simple threshold, `"internal.container.failure.threshold"` set the
-limit for the number of container failures tolerated for the life of an application.
-
-This has now been reworked to support
-# a time-bounded window for failures
-# placement in `resources.json` as `"yarn.container.failure.threshold"`
-# reset/changing during cluster flex
-# Configurable in a combination of days, hours and minutes.
-
-This is a major change —and is necessary to support long-lived applications with
-a slow failure rate, while still detecting and reacting to the situation where
-many containers are failing in a short period of time.
-
-Because the property name has changed, any cluster where this had been changed from
-the default (which is still five) will not pick up the changes. Please use the
-new name and set the value in the global section of `resources.json`
+TBD
 
 ## Other changes
 
-The full list of completed issues is [visible in the Apache JIRA](https://issues.apache.org/jira/browse/SLIDER/fixforversion/12326949/)
+The full list of completed issues is [visible in the Apache JIRA](https://issues.apache.org/jira/browse/SLIDER/fixforversion/12327198/)