From general-return-28426-apmail-incubator-general-archive=incubator.apache.org@incubator.apache.org Sat May 21 02:15:15 2011 Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7655041F6 for ; Sat, 21 May 2011 02:15:15 +0000 (UTC) Received: (qmail 49267 invoked by uid 500); 21 May 2011 02:15:14 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 49064 invoked by uid 500); 21 May 2011 02:15:14 -0000 Mailing-List: contact general-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 general@incubator.apache.org Received: (qmail 49049 invoked by uid 99); 21 May 2011 02:15:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2011 02:15:14 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [128.149.139.106] (HELO mail.jpl.nasa.gov) (128.149.139.106) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 21 May 2011 02:15:02 +0000 Received: from mail.jpl.nasa.gov (altvirehtstap02.jpl.nasa.gov [128.149.137.73]) by smtp.jpl.nasa.gov (Switch-3.4.3/Switch-3.4.3) with ESMTP id p4L2Eb2W023799 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Fri, 20 May 2011 19:14:38 -0700 Received: from ALTPHYEMBEVSP20.RES.AD.JPL ([128.149.137.82]) by ALTVIREHTSTAP02.RES.AD.JPL ([128.149.137.73]) with mapi; Fri, 20 May 2011 19:14:37 -0700 From: "Mattmann, Chris A (388J)" To: "lucy-dev@incubator.apache.org" CC: "general@incubator.apache.org" Date: Fri, 20 May 2011 19:14:19 -0700 Subject: Re: [lucy-dev] [VOTE] Apache Lucy 0.1.0-incubating release candidate #1 Thread-Topic: [lucy-dev] [VOTE] Apache Lucy 0.1.0-incubating release candidate #1 Thread-Index: AcwXXNVCeMrCmkW6Se6QMnm9w2Krog== Message-ID: References: <7260622D-AFDD-4BF4-9E7C-32E4B1FF01A2@jpl.nasa.gov> <20110520214412.GB11435@rectangular.com> <422D2127-C6F5-4647-AE54-CA3E7B8CB023@jpl.nasa.gov> <477033.42175.qm@web161405.mail.bf1.yahoo.com> In-Reply-To: <477033.42175.qm@web161405.mail.bf1.yahoo.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Source-IP: altvirehtstap02.jpl.nasa.gov [128.149.137.73] X-Source-Sender: chris.a.mattmann@jpl.nasa.gov X-AUTH: Authorized X-Virus-Checked: Checked by ClamAV on apache.org Okey dokey, in the interest of just getting the RC out and moving onto the = next set of things to get done, RC 2 coming up... Cheers, Chris On May 20, 2011, at 6:43 PM, Joe Schaefer wrote: > RM docs are always guides, not decrees, but Marvin is > certainly within his rights to vote according to the > current docs. Keep in mind noone gets to veto a release > (unless it's on legal grounds, and those should be rare). >=20 > FWIW, I think the full 3-part version string belongs > in the package name, while the 2-part version string > belongs in the branch, as that is the point of creating > the branch in the first place- so you can cut maintainence > releases from it that are just patch-level changes. Unfortunately > CPAN won't be very happy about it, but it's a manageable > problem. >=20 > The tag issue for rc's I am ambivalent about personally. >=20 > But basically I agree with the existing Lucy docs. In the interest > of time, since I know you don't have much more you can spare > on this effort, I suggest you try to just follow them as-is. > And lets keep the initial voting confined to dev@lucy as > Marvin suggests. >=20 >=20 >=20 > ----- Original Message ---- >> From: "Mattmann, Chris A (388J)" >> To: "general@incubator.apache.org" >> Cc: "lucy-dev@incubator.apache.org" ;=20 >> "lucy-user@incubator.apache.org" >> Sent: Fri, May 20, 2011 9:30:52 PM >> Subject: Re: [lucy-dev] [VOTE] Apache Lucy 0.1.0-incubating release cand= idate=20 >> #1 >>=20 >> Hi Marvin, >>=20 >> On May 20, 2011, at 2:44 PM, Marvin Humphrey wrote: >>=20 >>> Hi, Chris, thanks for expediting. >>>=20 >>> On Fri, May 20, 2011 at 02:18:37PM -0700, Mattmann, Chris A (388J) wro= te: >>>> http://people.apache.org/~mattmann/apache-lucy-0.1-incubating/rc1/ >>>=20 >>> The artifacts here do not follow the version naming convention that is = used=20 >> by >>> the source code of X.Y.Z, and that the ReleaseGuide specifies the arti= facts >>> should use: >>>=20 >>> apache-lucy-0.1-incubating-src.tar.gz // actual name >>> apache-lucy-incubating-X.Y.Z.tar.gz // documented in ReleaseGu= ide. >>=20 >> Hmmm....Sorry but this is the first time I've carefully looked at the=20 >> ReleaseGuide, otherwise if I saw it back when you threw it up on the wi= ki, I'd=20 >> probably have debated this convention for *artifact names* (note this a= n=20 >> important distinction -- I'm not debating the programmatic use of versi= on #s as=20 >> is covered below). Most of the Apache releases I've seen use *artifact = names* =20 >> likes: >>=20 >> apache---. >>=20 >> In this case, we're the lucy product, version 0.1-incubating, it's a sr= c=20 >> release, and it's a tar.gz extension. >>=20 >> I think that makes more sense than: >>=20 >> apache--incubating-. >>=20 >>>=20 >>> It's essential that our artifacts match the actual version number stri= ngs. >>=20 >> Who are you talking about when you say "our"? I am included in that set= ? If=20 >> so, I'm not necessarily on board with your proposal for what the *artfi= act=20 >> name* should be. Note that the discussion we had on your referenced thr= ead=20 >> below is actually talking about programmatic uses of a string/int/number= =20 >> version within the context of PL-specific forges like CPAN/Maven =20 >> Central/PyPI/etc. It's not talking about artifact names. >>=20 >>> This was hammered out over a long thread here: . >>>=20 >>> The branch we will use for bugfixes is also misnamed: >>>=20 >>> // Actual name >>>=20 >> https://svn.apache.org/repos/asf/incubator/lucy/branches/apache-lucy-0.1= -incubating/ >>=20 >>> // Documented in ReleaseGuide >>> https://svn.apache.org/repos/asf/incubator/lucy/branches/X.Y >>=20 >> Gotcha. I transposed the branch and tag names. >>=20 >> Speaking of which though, let me also poke at this. Having 2 convention= s for=20 >> tags and branches seems odd to me and it seems like the introduction of= =20 >> pointless complexity for little gain. Why not just pick one: >>=20 >> either: >>=20 >> apache-lucy-X.Y (e.g., apache-lucy-0.1-incubating) >>=20 >> or: >>=20 >> X.Y (e.g., 0.1-incubating) >>=20 >> Having 2 conventions for branches and tags seems odd to me.=20 >>=20 >>>=20 >>> And there is no tag for the RC as the instructions set out: >>>=20 >>>=20 >> https://svn.apache.org/repos/asf/incubator/lucy/tags/apache-lucy-incubat= ing-X.Y.Z-rcN >>=20 >>=20 >> IMO and experience, tags are created when a release VOTE passes to capt= ure a =20 >> *final* snapshot of the release that's not expected to change. Some othe= r =20 >> projects use tags as the first release VOTE'ing artifact, and then roll = a branch =20 >> when the VOTE passes to indicate further development in a series. Either= way is =20 >> fine. I'm happy to create the tag, but honestly, this approach seems lik= e an RM =20 >> decision to me and something that we should leave open to the guy pickin= g up a =20 >> shovel and doing the RM'ing. >>=20 >>>=20 >>> I regret that I must vote -1. Please change the name of the tag, foll= owing >>> the documentation in the ReleaseGuide precisely and reroll. If you=20 > disagree >>> with anything you encounter, please raise your concern on the dev list= . >>=20 >> No probs. Concerns raised above.=20 >>=20 >> Cheers, >> Chris >>=20 >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Chris Mattmann, Ph.D. >> Senior Computer Scientist >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >> Office: 171-266B, Mailstop: 171-246 >> Email: chris.a.mattmann@nasa.gov >> WWW: http://sunset.usc.edu/~mattmann/ >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >> Adjunct Assistant Professor, Computer Science Department >> University of Southern California, Los Angeles, CA 90089 USA >> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ >>=20 >>=20 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Chris Mattmann, Ph.D. Senior Computer Scientist NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA Office: 171-266B, Mailstop: 171-246 Email: chris.a.mattmann@nasa.gov WWW: http://sunset.usc.edu/~mattmann/ ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Adjunct Assistant Professor, Computer Science Department University of Southern California, Los Angeles, CA 90089 USA ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org