hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Todd Papaioannou <to...@yahoo-inc.com>
Subject Re: [DISCUSS] Hadoop Security Release off Yahoo! patchset
Date Tue, 18 Jan 2011 02:55:22 GMT
That's only true if you plan to pull forward the changes wholesale into .21, .22 and beyond.
And that is not what is being proposed.

If the plan is to just land an updated and more stable version of .20 that is completely backwards
compatible, then this can be done within that code line without any impact to the end users.
Any changes that the community wish to pull forward can be identified, isolated and reviewed
per the normal process. Or they can remain in the .20.100 release for eternity, without any
impact on the future.

Either way, the .20 release will be more stable, performant and more useful to our users,
and the community at large can focus on releasing .22, which we all believe is the right goal.


From: Doug Cutting <cutting@apache.org<mailto:cutting@apache.org>>
Reply-To: "general@hadoop.apache.org<mailto:general@hadoop.apache.org>" <general@hadoop.apache.org<mailto:general@hadoop.apache.org>>
Date: Mon, 17 Jan 2011 15:49:51 -0800
To: "general@hadoop.apache.org<mailto:general@hadoop.apache.org>" <general@hadoop.apache.org<mailto:general@hadoop.apache.org>>
Subject: Re: [DISCUSS] Hadoop Security Release off Yahoo! patchset

Backwards compatibility has been a goal, so
with luck we will not ID regressions.

My point was that, in addition to back-compatibility with prior 0.20
releases, we must also consider the forward-compatibility of each change
with 0.21, 0.22 and trunk.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message