Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 56376 invoked from network); 10 Jun 2004 06:39:25 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 10 Jun 2004 06:39:25 -0000 Received: (qmail 76423 invoked by uid 500); 10 Jun 2004 06:39:48 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 76375 invoked by uid 500); 10 Jun 2004 06:39:47 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 76362 invoked by uid 99); 10 Jun 2004 06:39:47 -0000 Received: from [216.6.48.60] (HELO ags01.agsoftware.dnsalias.com) (216.6.48.60) by apache.org (qpsmtpd/0.27.1) with ESMTP; Wed, 09 Jun 2004 23:39:47 -0700 Received: from ags01.agsoftware.dnsalias.com (localhost.localdomain [127.0.0.1]) by ags01.agsoftware.dnsalias.com (8.12.10/8.12.10) with ESMTP id i5A6d998015081 for ; Thu, 10 Jun 2004 00:39:09 -0600 Received: (from apache@localhost) by ags01.agsoftware.dnsalias.com (8.12.10/8.12.10/Submit) id i5A6d9oK015079; Thu, 10 Jun 2004 00:39:09 -0600 X-Authentication-Warning: ags01.agsoftware.dnsalias.com: apache set sender to agallardo@agssa.net using -f Received: from 10.0.0.5 (SquirrelMail authenticated user agallardo); by ags01.agsoftware.dnsalias.com with HTTP; Thu, 10 Jun 2004 00:39:09 -0600 (CST) Message-ID: <36208.10.0.0.5.1086849549.squirrel@10.0.0.5> Date: Thu, 10 Jun 2004 00:39:09 -0600 (CST) Subject: The never coming final release 1.0 From: "Antonio Gallardo" To: ojb-dev@db.apache.org User-Agent: SquirrelMail/1.4.3a-0.f1.1 X-Mailer: SquirrelMail/1.4.3a-0.f1.1 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi: For more than a year, many of us were waiting for the OJB final 1.0. My perception is that it is a non reacheable target. There is just another stuff or change need to be done and each of them seems to be so important that need to be included in the "final 1.0". We have already 6 release candidates and seems none of them was good enough to be a final 1.0 release. I don't think so. I am writing no because someone is pushing my back telling me that I need to have a final 1.0 release in my hands. But because I see a problem: The never released final 1.0 is freezing further OJB development. I often see comments like: "This feature need to wait after 1.0 is release..." I think it is time to seriously consider making a 1.0 release and stop freezeing futher development. As I often hear: "Sometimes less is better". I hope nobody will take this post as a personal rant. I really appreciate the OJB community and the effort that the development team is doing. Please take this message in the best sense you can. And think about that. ;-) Best Regards, Antonio Gallardo. --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org