Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C4A4ED25B for ; Wed, 22 May 2013 21:25:03 +0000 (UTC) Received: (qmail 66005 invoked by uid 500); 22 May 2013 21:25:01 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 65925 invoked by uid 500); 22 May 2013 21:25:01 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 65917 invoked by uid 99); 22 May 2013 21:25:01 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 21:25:01 +0000 Received: from localhost (HELO mail-pd0-f174.google.com) (127.0.0.1) (smtp-auth username cdouglas, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 May 2013 21:25:01 +0000 Received: by mail-pd0-f174.google.com with SMTP id 3so338178pdj.33 for ; Wed, 22 May 2013 14:25:00 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nhvwNmBWKroMmHmFc4Wg959VY4Jnv0L+DDAcOmGvWnM=; b=B7kBkGzUK8VkNJwev0yg0rogYiTVjXTM3gwSg954Gu8STP5QVXFeqx5gEcNiuLT5eY 2InZydEclPYwBdIYKKO1ynBG9OPzxdapj4YM4c1ABnsMKm+Cqx5eICr2TpoeWBNji5T3 aZRFDssglrFTLifK1bPKamuYROMEQU/m15gPXfIc9WYrxew9iQY6ppstmRQpkUVZcPzb BAWXNfTjRmqnjarm68yRaW4VlISkYAuj1B1p6qkLbAAsre0fEwVRuHepLoC7nPL18u8a MH9KLfaPNXcxYAk5hiXsP4igUMidpz6wMmmJKnYuvnL6ZXMOOg/j1AcOXq5VfLWfJD1/ /bNw== MIME-Version: 1.0 X-Received: by 10.66.121.132 with SMTP id lk4mr10427782pab.1.1369257900728; Wed, 22 May 2013 14:25:00 -0700 (PDT) Received: by 10.68.233.1 with HTTP; Wed, 22 May 2013 14:25:00 -0700 (PDT) In-Reply-To: References: Date: Wed, 22 May 2013 14:25:00 -0700 Message-ID: Subject: Re: [ANNOUNCE] Hadoop version 1.2.0 released From: Chris Douglas To: "general@hadoop.apache.org" Content-Type: text/plain; charset=ISO-8859-1 As always, thank you for seeing this through, Matt. -C On Wed, May 22, 2013 at 1:19 PM, Matt Foley wrote: > It appears to be propagating slowly but effectively. Hopefully by tomorrow > it should be done. If it isn't, I'll provide more info, otherwise will > consider the issue closed. > Thanks, > --Matt > > > On Wed, May 22, 2013 at 1:12 PM, Matt Foley wrote: > >> It came to my attention yesterday (thanks, Arpit Gupta) that even though I >> had gone through the process on Nexus to publish the release, the 1.2.0 >> artifacts were not in fact Released in Nexus. >> >> I attempted to fix the issue yesterday afternoon, but it didn't work. The >> artifacts are still stuck in "Staging". I will continue to work on it; >> sorry for any inconvenience in the meantime. >> >> Regards, >> --Matt >> >> >> On Wed, May 15, 2013 at 12:32 AM, Matt Foley wrote: >> >>> I'm happy to announce that on May 13, Hadoop version 1.2.0 passed its >>> release vote. It is now available in SVN and is in process of propagating >>> to artifact mirrors. It should be available on all mirrors by end of day >>> Wednesday. >>> >>> This release delivers over 200 enhancements and bug-fixes, compared to >>> the previous 1.1.2 release. Major enhancements include: >>> >>> - DistCp v2 backported >>> - Web services for JobTracker >>> - WebHDFS enhancements >>> - Extensions of task placement and replica placement policy interfaces >>> - Offline Image Viewer backported >>> - Namenode more robust in case of edit log corruption >>> - Add NodeGroups level to NetworkTopology >>> - Add "unset" to Configuration API >>> >>> Please see the Hadoop 1.2.0 Release Notes for >>> more details. >>> >>> This is a beta release. I intend to start a stabilization release >>> (version 1.2.1) in 3 weeks from now. >>> >>> All open Jira tickets with Target Version "1.2.0" that weren't yet >>> closed, were moved to Target Version 1.3.0. However, if you want something >>> fixed in 1.2.1, you are encouraged to edit that ticket, change its Target >>> Version to 1.2.1, and contribute a patch to branch-1.2. Bug fixes are >>> welcome in 1.2.1. However, we ask that significant feature enhancements be >>> contributed to branch-1 for the future version 1.3.0, instead. >>> >>> Thank you, and enjoy your new release. >>> Best regards, >>> --Matt >>> (release manager, version 1.2) >>> >> >>