Return-Path: Delivered-To: apmail-jakarta-ant-dev-archive@apache.org Received: (qmail 73035 invoked from network); 7 Jan 2003 14:13:57 -0000 Received: from exchange.sun.com (192.18.33.10) by daedalus.apache.org with SMTP; 7 Jan 2003 14:13:57 -0000 Received: (qmail 15873 invoked by uid 97); 7 Jan 2003 14:15:12 -0000 Delivered-To: qmlist-jakarta-archive-ant-dev@jakarta.apache.org Received: (qmail 15856 invoked by uid 97); 7 Jan 2003 14:15:11 -0000 Mailing-List: contact ant-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list ant-dev@jakarta.apache.org Received: (qmail 15844 invoked by uid 98); 7 Jan 2003 14:15:11 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) Message-ID: <3E1AE25C.1090308@cortexebusiness.com.au> Date: Wed, 08 Jan 2003 01:21:16 +1100 From: Conor MacNeill User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003 X-Accept-Language: en-us, en-au MIME-Version: 1.0 To: Ant Developers List Subject: Release Plans Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N I'd like to kick off a discussion about the next few Ant releases, what they contain and what timeframes etc. I think there is broad agreement on a 1.5.2 release pretty soon. I'd like to make that the last 1.5 branch release as working on both branches is not really efficient. Actually, my original intention was that branches would be short lived and merges occur only around dot release points. The next release to consider, is therefore 1.6. It has a number of pretty core changes so far - top level tasks, the import task, the new project helper, namespace support. I think we are pretty close to some form of antlib system too. I'd also like to get some sort of polymorphism in there, although that is less sure, at this time. I don't think there should be much in the way of other major structural changes in the core for this release. There will of course be continuing bug fixes to core and tasks as always. I would, however, like to put a fair bit of effort into trying out and testing these new features to make sure they work as we want them to before committing them to a release. I think there are probably a few interesting interactions we need to sort out :-) As for timeframes, I'd try for the 1.5.2 release by end January and a 1.6 release by end May, maybe earlier. This is not a vote, just a discussion starter to give us something to work with. Thoughts? Conor -- To unsubscribe, e-mail: For additional commands, e-mail: