Return-Path: Delivered-To: apmail-db-jdo-dev-archive@www.apache.org Received: (qmail 12777 invoked from network); 20 Mar 2008 11:55:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Mar 2008 11:55:43 -0000 Received: (qmail 84281 invoked by uid 500); 20 Mar 2008 11:55:40 -0000 Mailing-List: contact jdo-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: jdo-dev@db.apache.org Delivered-To: mailing list jdo-dev@db.apache.org Received: (qmail 84270 invoked by uid 99); 20 Mar 2008 11:55:40 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2008 04:55:40 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of davejrdn@bellsouth.net designates 204.127.217.104 as permitted sender) Received: from [204.127.217.104] (HELO fmailhost04.isp.att.net) (204.127.217.104) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Mar 2008 11:54:48 +0000 Received: from [192.168.0.161] (adsl-065-013-157-128.sip.rdu.bellsouth.net[65.13.157.128]) by isp.att.net (frfwmhc04) with SMTP id <20080320115508H0400a0nupe>; Thu, 20 Mar 2008 11:55:08 +0000 X-Originating-IP: [65.13.157.128] In-Reply-To: <47E02F95.6080508@sun.com> References: <47E02F95.6080508@sun.com> Mime-Version: 1.0 (Apple Message framework v753) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Cc: JDO Expert Group , Apache JDO project Content-Transfer-Encoding: 7bit From: David Jordan Subject: Re: [VOTE] Release Apache JDO 2.1 Date: Thu, 20 Mar 2008 07:55:06 -0400 To: Michelle Caisse X-Mailer: Apple Mail (2.753) X-Virus-Checked: Checked by ClamAV on apache.org +1 on the release... I was not happy to see the following bad news... http://www.informationweek.com/software/showArticle.jhtml? articleID=206904549 Sun does not seem to make any sense these days. They have sponsored the best API, JDO, for years. Then they let the EJB folks create JPA, which they tried to get to subsume JDO. Now they go with TopLink, an Oracle product, right after they have bought JBoss? It just makes no sense. On Mar 18, 2008, at 5:09 PM, Michelle Caisse wrote: > This vote is to release the Apache JDO 2.1 specification, TCK, and > API (both legacy and current versions) with the projects that they > depend on: enhancer, model, and util. > > [+1] Release JDO 2.1 specification, api, tck, enhancer, model, and > util > [0] Don't care > [-1] Don't releaseJDO 2.1 specification, api, tck, enhancer, model, > and util because: > > > > The specification is available at http://db.apache.org/jdo/ > specifications.html. The TCK can be tested from the staging area, > http://people.apache.org/~mcaisse/jdo2.1-rc2/dist. Please follow > the directions at http://wiki.apache.org/jdo/ReleaseTesting2dot1 > for downloading and testing. It would be useful if you would record > the results of your testing there. > > Please test and vote. Voting will close at noon PDT Monday, March 24. > > -- Michelle >