Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8E10D200BF0 for ; Fri, 30 Dec 2016 17:10:14 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 8C9BA160B32; Fri, 30 Dec 2016 16:10:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id D544B160B24 for ; Fri, 30 Dec 2016 17:10:13 +0100 (CET) Received: (qmail 24439 invoked by uid 500); 30 Dec 2016 16:10:13 -0000 Mailing-List: contact cvs-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list cvs@incubator.apache.org Received: (qmail 24430 invoked by uid 99); 30 Dec 2016 16:10:13 -0000 Received: from Unknown (HELO svn01-us-west.apache.org) (209.188.14.144) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 30 Dec 2016 16:10:13 +0000 Received: from svn01-us-west.apache.org (localhost [127.0.0.1]) by svn01-us-west.apache.org (ASF Mail Server at svn01-us-west.apache.org) with ESMTP id 3D7DD3A0617 for ; Fri, 30 Dec 2016 16:10:12 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r1776598 - in /incubator/public/trunk/content: 2017-logo-contest.xml guides/draft-simple-release-management.xml Date: Fri, 30 Dec 2016 16:10:11 -0000 To: cvs@incubator.apache.org From: johndament@apache.org X-Mailer: svnmailer-1.0.9 Message-Id: <20161230161012.3D7DD3A0617@svn01-us-west.apache.org> archived-at: Fri, 30 Dec 2016 16:10:14 -0000 Author: johndament Date: Fri Dec 30 16:10:11 2016 New Revision: 1776598 URL: http://svn.apache.org/viewvc?rev=1776598&view=rev Log: Updating logo page to remove instance. Updating release management page with clearer text. Modified: incubator/public/trunk/content/2017-logo-contest.xml incubator/public/trunk/content/guides/draft-simple-release-management.xml Modified: incubator/public/trunk/content/2017-logo-contest.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/2017-logo-contest.xml?rev=1776598&r1=1776597&r2=1776598&view=diff ============================================================================== --- incubator/public/trunk/content/2017-logo-contest.xml [utf-8] (original) +++ incubator/public/trunk/content/2017-logo-contest.xml [utf-8] Fri Dec 30 16:10:11 2016 @@ -60,7 +60,7 @@ limitations under the License.

Here are some straight forward steps to submit your logo

    -
  • Create an account on the ASF JIRA Instance (if you don't already have one)
  • +
  • Create an account on the ASF JIRA (if you don't already have one)
  • Create an issue on the Incubator Project
  • Click Next
  • Create a ticket, with the following information: Modified: incubator/public/trunk/content/guides/draft-simple-release-management.xml URL: http://svn.apache.org/viewvc/incubator/public/trunk/content/guides/draft-simple-release-management.xml?rev=1776598&r1=1776597&r2=1776598&view=diff ============================================================================== --- incubator/public/trunk/content/guides/draft-simple-release-management.xml [utf-8] (original) +++ incubator/public/trunk/content/guides/draft-simple-release-management.xml [utf-8] Fri Dec 30 16:10:11 2016 @@ -66,13 +66,15 @@ limitations under the License.

    It is well understood that one of the goals of incubation is to help a podling understand how to - build ASF compliant releases. This is why its important to have - mentors - and other + build ASF compliant releases. This is why its + mandatory to have at least 3 +1 votes from IPMC members - review the releases for accuracy in compliance with the ASF and Incubator policies. Those reviewing the releases will provide the release managers - with information about what is wrong with the release. Release managers should consider issues reported as blocking, unless told otherwise - by those reporting the issue. + review the releases (this should include your mentors but is not mandatory) + for accuracy in compliance with the ASF and Incubator policies. + The podling community, of course, needs to be fully engaged in review process as well. Anybody reviewing + the releases will provide the release manager and IPMC members with information about what is wrong + with the release. The severity of the issues and whether they are blocking or not may be discussed + but the ultimate guidance on where podling releases may get additional flexibility belongs to the mentors and IPMC members.

    --------------------------------------------------------------------- To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org For additional commands, e-mail: cvs-help@incubator.apache.org