+1 on EOL of branch-2.9.
Since there are a lot of backported fixes in branch-2.10 after 2.10.0
(2019 Oct 29),
it would be nice to release 2.10.1.
I'm happy to help release work.
Masatake Iwasaki
On 2020/08/28 3:25, Mingliang Liu wrote:
are there any Hadoop branch-2 releases planned, ever? If so I'll need to
backport my s3a directory compatibility patch to whatever is still live.
The branch-2 is gone. I think you mean branch-2.10, Steve.
Many HBase users are still using Hadoop 2, so I hope Hadoop 2.10.x should
still be released at least every 12 months. If there is no volunteer for
2.10.1 RM, I can see how I can help.
Thanks,
On Thu, Aug 27, 2020 at 8:55 AM John Zhuge <jzh...@apache.org> wrote:
+1
On Thu, Aug 27, 2020 at 6:01 AM Ayush Saxena <ayush...@gmail.com> wrote:
+1
-Ayush
On 27-Aug-2020, at 6:24 PM, Steve Loughran <ste...@cloudera.com.invalid
wrote:
+1
are there any Hadoop branch-2 releases planned, ever? If so I'll need
to
backport my s3a directory compatibility patch to whatever is still live.
On Thu, 27 Aug 2020 at 06:55, Wei-Chiu Chuang <weic...@apache.org>
wrote:
Bump up this thread after 6 months.
Is anyone still interested in the 2.9 release line? Or are we good to
start
the EOL process? The 2.9.2 was released in Nov 2018.
I'd really like to see the community to converge to fewer release
lines
and
make more frequent releases in each line.
Thanks,
Weichiu
On Fri, Mar 6, 2020 at 5:47 PM Wei-Chiu Chuang <weic...@apache.org>
wrote:
I think that's a great suggestion.
Currently, we make 1 minor release per year, and within each minor
release
we bring up 1 thousand to 2 thousand commits in it compared with the
previous one.
I can totally understand it is a big bite for users to swallow.
Having a
more frequent release cycle, plus LTS and non-LTS releases should
help with
this. (Of course we will need to make the release preparation much
easier,
which is currently a pain)
I am happy to discuss the release model further in the dev ML. LTS
v.s.
non-LTS is one suggestion.
Another similar issue: In the past Hadoop strived to
maintain compatibility. However, this is no longer sustainable as
more CVEs
coming from our dependencies: netty, jetty, jackson ... etc.
In many cases, updating the dependencies brings breaking changes.
More
recently, especially in Hadoop 3.x, I started to make the effort to
update
dependencies much more frequently. How do users feel about this
change?
On Thu, Mar 5, 2020 at 7:58 AM Igor Dvorzhak <i...@google.com.invalid
wrote:
Maybe Hadoop will benefit from adopting a similar release and
support
strategy as Java? I.e. designate some releases as LTS and support
them for
2 (?) years (it seems that 2.7.x branch was de-facto LTS), other
non-LTS
releases will be supported for 6 months (or until next release).
This
should allow to reduce maintenance cost of non-LTS release and
provide
conservative users desired stability by allowing them to wait for
new LTS
release and upgrading to it.
On Thu, Mar 5, 2020 at 1:26 AM Rupert Mazzucco <
rupert.mazzu...@gmail.com>
wrote:
After recently jumping from 2.7.7 to 2.10 without issue myself, I
vote
for keeping only the 2.10 line.
It would seem all other 2.x branches can upgrade to a 2.10.x
easily
if
they feel like upgrading at all,
unlike a jump to 3.x, which may require more planning.
I also vote for having only one main 3.x branch. Why are there
3.1.x and
3.2.x seemingly competing,
and now 3.3.x? For a community that does not have the resources to
manage multiple release lines,
you guys sure like to multiply release lines a lot.
Cheers
Rupert
Am Mi., 4. März 2020 um 19:40 Uhr schrieb Wei-Chiu Chuang
<weic...@cloudera.com.invalid>:
Forwarding the discussion thread from the dev mailing lists to
the
user
mailing lists.
I'd like to get an idea of how many users are still on Hadoop
2.9.
Please share your thoughts.
On Mon, Mar 2, 2020 at 6:30 PM Sree Vaddi
<sree_at_ch...@yahoo.com.invalid> wrote:
+1
Sent from Yahoo Mail on Android
On Mon, Mar 2, 2020 at 5:12 PM, Wei-Chiu Chuang<
weic...@apache.org>
wrote: Hi,
Following the discussion to end branch-2.8, I want to start a
discussion
around what's next with branch-2.9. I am hesitant to use the
word
"end
of
life" but consider these facts:
* 2.9.0 was released Dec 17, 2017.
* 2.9.2, the last 2.9.x release, went out Nov 19 2018, which is
more
than
15 months ago.
* no one seems to be interested in being the release manager for
2.9.3.
* Most if not all of the active Hadoop contributors are using
Hadoop
2.10
or Hadoop 3.x.
* We as a community do not have the cycle to manage multiple
release
line,
especially since Hadoop 3.3.0 is coming out soon.
It is perhaps the time to gradually reduce our footprint in
Hadoop
2.x, and
encourage people to upgrade to Hadoop 3.x
Thoughts?
--
John Zhuge
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
