[From nobody Fri Aug 6 17:02:31 2004 Return-Path: <jhunter@servlets.com> Received: from randall.mail.atl.earthlink.net (randall.mail.atl.earthlink.net [207.69.200.237]) by jhunter.xquery.com (8.12.8/8.12.9) with ESMTP id i167QHoZ020272 for <jhunter@xquery.com>; Thu, 5 Feb 2004 23:26:17 -0800 Received: from watson.mail.atl.earthlink.net ([207.69.200.154]) by randall.mail.atl.earthlink.net with smtp (Exim 3.33 #1) id 1Ap1zB-0007C4-00 for jhunter@xquery.com; Fri, 06 Feb 2004 04:09:17 -0500 X-MindSpring-Loop: servlets@mindspring.com Received: from mail3.firstlink.com ([66.37.141.15]) by watson.mail.atl.earthlink.net (EarthLink SMTP Server) with ESMTP id 1aP1Z9c93Nl3qW0 for <servlets@mindspring.com>; Fri, 6 Feb 2004 04:09:14 -0500 (EST) Received: from relay3.firstlink.com (relay3.firstlink.com [66.37.141.30]) by mail3.firstlink.com (Postfix) with ESMTP id 3410A126704 for <jhunter@servlets.com>; Fri, 6 Feb 2004 02:09:14 -0700 (MST) Received: from localhost (localhost [127.0.0.1]) by relay3.firstlink.com (Postfix) with ESMTP id 067DED8BAF for <jhunter@servlets.com>; Fri, 6 Feb 2004 02:09:14 -0700 (MST) Received: from relay3.firstlink.com ([127.0.0.1]) by localhost (relay3.firstlink.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 99137-09 for <jhunter@servlets.com>; Fri, 6 Feb 2004 02:09:02 -0700 (MST) Received: from snowball.huntershots.com (unknown [65.122.201.44]) by relay3.firstlink.com (Postfix) with ESMTP id 62D6CD8BB9 for <jhunter@servlets.com>; Fri, 6 Feb 2004 02:09:01 -0700 (MST) Received: from servlets.com (snowball [192.168.1.4]) by snowball.huntershots.com (8.12.9/8.12.2) with ESMTP id i169CZ94006071; Fri, 6 Feb 2004 01:12:35 -0800 (PST) Message-ID: <402359AD.5000307@servlets.com> Date: Fri, 06 Feb 2004 01:09:01 -0800 From: Jason Hunter <jhunter@servlets.com> User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "jdom-interest@jdom.org" <jdom-interest@jdom.org> Subject: Announcing JDOM b10-rc1 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by First Link Technology, Inc. X-Spam-Status: No, hits=-12.5 required=5.0 tests=BAYES_01,TO_ADDRESS_EQ_REAL,USER_AGENT_MOZILLA_UA autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Good news! After today's work I'm proud to report there are NO known API changes required before our 1.0 release. What we have now is my best effort at a 1.0 release API. We may still have bugs or inconsistencies, but the TODO is wiped clean of everything I personally deem important enough to stand in the way of a long, long, long awaited 1.0 release. My goal is to get us to a 1.0 release in the next 6 weeks. Here's my plan. I've posted on jdom.org a Beta10 Release Candidate #1. It's built from the very latest CVS source. You can get it at http://jdom.org/dist/source/jdom-b10-rc1.zip. I'd like people who are using b9 to download this and see how things work. Please double check everything's still prim and proper and performant. The code passes all the jdom-test cases, but they don't have great coverage (although they did help me find a bug earlier tonight). Subclassers: I'm especially interested in hearing your feedback since we restricted a lot of visibilities. Then I'd like people who've been involved in the API design to thoroughly scour the new Javadocs (online also at http://jdom.org/docs/apidocs/). Do all the new structures make sense? Is everything consistent? Once we're satisfied this b10-rc1 code and interface is correct (in perhaps one to two weeks), we'll ship the formal Beta10. After that, we'll get started on the 1.0 Release Candidates. The first 1.0-rc1 will be Beta10 minus the deprecated methods. (We need to ship 1.0 without any deprecations.) We'll try to spread the word to everyone that 1.0 is coming and make sure people test their code against it. We'll have a month to iron out any issues. Throughout this process, API corrections will be more important than code corrections. I'm happy to ship a 1.0.1 with code fixes, but I want the 1.0 API as solid as possible. We've done a bunch of changes since b9, so there's a lot to review. Sound good? When we ship 1.0, I'll collect all those beers. :-) -jh- ]