Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (nike.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gbiv.com; h=content-type
	:mime-version:subject:from:in-reply-to:date
	:content-transfer-encoding:message-id:references:to; q=dns; s=
	gbiv.com; b=oLdsd6DY1cYOHGlSBXMdpEgoDA0sXjLc4DskLKYsLSi4IHKAoeb4
	zbgFtDB0Wh+KHPH/Gs9p9imgjExOWo/sQcuAarSFjrAsp1RB+5hFZIr6sCKSjvr4
	2ksVw9EJS4vXUrQevo9kncTC559CVrWPDAVOP+0khllo/nf5L0j54sg=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: [DISCUSSION] Thinking about 20.204 and beyond 
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <4E18CE25-6863-4318-8A95-17896B0B87D1@yahoo-inc.com>
Date: Sat, 18 Jun 2011 13:22:14 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <0C4895F3-95E8-45ED-B2B0-C3BF4B5436B1@gbiv.com>
References: <4E18CE25-6863-4318-8A95-17896B0B87D1@yahoo-inc.com>
To: general@hadoop.apache.org

On Jun 17, 2011, at 11:50 PM, Eric Baldeschwieler wrote:

> Along with starting a new release off the mainline (see previous =
mail), the Yahoo! team plans to continue producing sustaining releases =
off the Hadoop with security branch, such as 0.20.203 .  I'm writing =
this email to outline our plans, explain Yahoo's motivation for =
supporting this work and request feedback and hopefully your =
endorsement.  This initiative stems from Yahoo's commitment to do its =
hadoop work in Apache and discontinue the Yahoo Distribution of Hadoop =
(http://yhoo.it/i9Ww8W).

Eric,

Please make an effort to understand that we act at Apache as =
individuals.
That includes you and your team.  Yes, everyone greatly appreciates the
fact that Yahoo! pays your salaries.  Nevertheless, here you are called
an individual named Eric.

Companies do not have motivations.  You do.  There is nothing wrong with
each and every individual here being motivated, at least partly, by what
their boss(es) consider the right path forward.  But you don't have to
sell it as something Yahoo! is doing, and you don't need to send =
marketing
messaging to the development lists at Apache.  Just be yourself and
represent yourself.

Anyone on the PMC can be an RM.  A package can be rolled at any time, =
and
a release vote on that package can be called at any time.  While it =
makes
sense for the individual planning to RM a release to announce their =
plans,
doing so does not in any way form the direction the product is headed,
nor does it exclude anyone else from being RM of their own release =
process.

There is absolutely no reason that trunk cannot be packaged for release
tomorrow as 0.23.  There may be many reasons why it won't pass a release
vote, but we probably aren't going to find them until somebody tries.

....Roy=