Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 10F949A33 for ; Wed, 18 Apr 2012 17:39:01 +0000 (UTC) Received: (qmail 62493 invoked by uid 500); 18 Apr 2012 17:39:00 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 62435 invoked by uid 500); 18 Apr 2012 17:39:00 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 62426 invoked by uid 99); 18 Apr 2012 17:39:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 18 Apr 2012 17:39:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of jopp@gmx.de designates 213.165.64.22 as permitted sender) Received: from [213.165.64.22] (HELO mailout-de.gmx.net) (213.165.64.22) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 18 Apr 2012 17:38:54 +0000 Received: (qmail invoked by alias); 18 Apr 2012 17:38:32 -0000 Received: from mnch-4d04780e.pool.mediaWays.net (EHLO [192.168.178.23]) [77.4.120.14] by mail.gmx.net (mp020) with SMTP; 18 Apr 2012 19:38:32 +0200 X-Authenticated: #351655 X-Provags-ID: V01U2FsdGVkX1/2XwE01wT2/z3BJ+Tmo2k8SYMN7Zj9zCj6mMOfPN 6QZ70k612YdOIP Message-ID: <4F8EFC17.2060804@gmx.de> Date: Wed, 18 Apr 2012 19:38:31 +0200 From: Christoph Jopp User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.28) Gecko/20120313 Lightning/1.0b2 Thunderbird/3.1.20 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: Has the AOO 3.4 RC been released? References: <002e01cd1d82$297b8fd0$7c72af70$@acm.org> In-Reply-To: X-Enigmail-Version: 1.1.2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-Virus-Checked: Checked by ClamAV on apache.org Am 18.04.2012 19:17, schrieb Kay Schenk: > On Wed, Apr 18, 2012 at 9:53 AM, Rob Weir wrote: > >> On Wed, Apr 18, 2012 at 6:41 PM, Dennis E. Hamilton >> wrote: >>> Michael, I am curious what has you be interested in the availability of >> an AOO 3.4 Release Candidate. >>> >>> 1. What does it say to you when a project build set is designated a >> "Release Candidate"? >>> >>> 2. What use would you make of such a designated build different from a >> developer snapshot and an actual release (i.e., AOO 3.4[.0])? >>> >> >> I wonder if there might be some language misunderstanding when we say >> casually, "We'll soon be voting on a Release Candidate"? >> >> To some this could mean we will have a vote to label a particular >> build as a "Release Candidate". That interpretation would explain >> some of the post we've been seeing. But that is not how it really >> works. >> >> What actually happens is two things: >> >> 1) The Release Manager (Juergen) declares that a particular build is >> the Release Candidate. >> >> 2) The PMC then votes on whether or not to release the Release Candidate. >> >> >> When we say "vote on a Release Candidate", some readers might think >> that we're voting to make the Release Candidate. But we're really >> voting to release the Release Candidate. Like when I vote for >> candidate for US President, I'm not voting to make him a candidate. >> I'm voting to make him President. >> > > A further point of clarification. Does "Release Candidate" in the ASF have > the same meaning as the traditional meaning. See, for example: > > http://en.wikipedia.org/wiki/Software_release_life_cycle#Release_candidate > > Given this definition, a Release Candidate means the "final" test before > the actual "release". > > So, to me, and perhaps others, a "release candidate" is NOT the same as a > release. And, to me, a "release candidate" as opposed to a "release" > implies some predetermined time announced to the public at large, for FINAL > testing -- seems like 2 weeks is typical. > > I am not sure at this point if this historical definition applies in the > ASF. > > I think it would be valuable to head up a new thread on this -- "What it > means to vote on a release candidate at the ASF" -- or something similar so > folks have a better understanding of "release candidates"/"release" at the > ASF. I might be totally wrong, but I think the main difference is that this project as long as it is a podling does not release anything. The one who releases is the Incubator project and the podling (PPMC) presents (after voting) the Incubator project a "candidate to be released". Then the Incubator project votes whether it should be officially released or not. So all that can be checked for bugs and regressions are the unofficial snapshots. Is this correct? Christoph > > >> >> -Rob >> >>> - Dennis >>> >>> >>> >>> -----Original Message----- >>> From: Michael Acevedo [mailto:vea1083@gmail.com] >>> Sent: Tuesday, April 17, 2012 11:36 >>> To: Apache OpenOffice >>> Subject: Has the AOO 3.4 RC been released? >>> >>> Hi, >>> >>> I was wondering if the AOO 3.4 Release Candidate is now available for >>> download? I see an entry in the Wiki that says so. >>> >>> Many Thanks >>> >>> -- >>> Best, >>> Michael >>> >> > > >