Without a public place to figure out which release will be EOL, it is very hard for users to choose the right releases to upgrade and develop.

This page tracks any release lines are EOL.

The process community followed is simple: If no volunteer to do a maintenance release in a short to mid-term (like 3 months to 1 or 1.5 year). We will claim a release is EOL. After EOL community can still choose to do a security-only release.

Following branches are EOL: 

[2.0.x - 2.9.x]

[3.0.x - 3.1.x]

And obviously, 1.x releases are all EOL.

Want to propose to EOL for more branches? Please start a discussion thread in dev email lists (YARN/MR/COMMON/HDFS) and get feedbacks from the community.


  • No labels

3 Comments

  1. Mingliang Liu

    Wei-Chiu Chuang Wangda Tan We still have old edge branches from where we cut for releases, for e.g. branch-2.3 ,... branch-2.8  Should we also delete those remote branches, so committers will get a clue what is happening when cherry-picking. Thanks,

  2. Akira Ajisaka

    Mingliang Liu The branches are protected, so we cannot remove those branches. Removing the source code is a workaround, and I removed that from branch-2. https://github.com/apache/hadoop/pull/1959

    1. Mingliang Liu

      Thanks Akira Ajisaka

      p.s. You just shared the largest PR I've ever seen.