1. Hadoop 2.0.5
Why it's important

3. Listing Profiles for Project: org.apache.giraph:giraph-parent
Profile Id: hadoop_0.20.203 (Active: true , Source: pom)
Profile Id: hadoop_1.0 (Active: false , Source: pom)
Profile Id: hadoop_non_secure (Active: false , Source: pom)
Profile Id: hadoop_facebook (Active: false , Source: pom)
Profile Id: hadoop_0.23 (Active: false , Source: pom)
Profile Id: hadoop_cdh4.1.2 (Active: false , Source: pom)
Profile Id: hadoop_yarn (Active: false , Source: pom)
Profile Id: hadoop_2.0.0 (Active: false , Source: pom)
Profile Id: hadoop_2.0.1 (Active: false , Source: pom)
Profile Id: hadoop_2.0.2 (Active: false , Source: pom)
Profile Id: hadoop_2.0.3 (Active: false , Source: pom)
Profile Id: hadoop_trunk (Active: false , Source: pom)
Profiles of actual ASF project

5. Why 2.0.5-α is important?
● 2.0.3-α is incompatible with 2.0.2-α
– 523 total; 12 incompatible changes
● 2.0.4-α
– 33 total; 0 incompatibilities
● 2.0.5-α
– 2 total; 0 incompatibilities

6. Is 2.0.5-α any good?
● Massively tested by BigTop platform

7. Hadoop roadmap
● 2.1.0-β is in woodworks
– 596 total; 41 incompatible changes
● First in the series
● Will be stabilized over time

8. When software is stable?
● Stable = unchanging
– Same behavior, functionality, APIs
● Bug fixes and security patches are Ok
● New functionality comes with upgrade
● “Some likes it hot”

9. Why one needs stable?
Left as an exercise for the reader

10. Contact: Samantha Leggat | t: 925.396.1194 | samantha.leggat@
wandisco.com
WANdisco, Bishop Ranch 8, 5000 Executive Pkwy, Suite 270, San Ramon, CA 94583
Thank you
cos@wandisco.com