I'd like to kick off a discussion on what needs to be done to get Ant 1.6 to a
release. I'm just going to ramble through some random thoughts I have been
having in no particular order just to get discussion started.
+1 on Conor to get the momentum rolling on this. It's tough to be psyched about working towards new releases when I personally run a CVS copy of Ant :)
1. Code cleanup
+1 on getting Checkstyle reports going so we can clean stuff up. I'll certainly chip in after seeing a report and do a bit of cleanup where I can.
4. xdocs proposal & manual generation
I'm not sure if this is still at the proposal stage or ready for primetime. I
think we probably won't progress unless we agree that this is the way to
generate the Ant manual and commit to supporting it as part of the standard
build process. If it is the way to go, I'd like to hurry it along.
There have been a couple of reasons why I have not hurried it along... 1) I'm ultra-busy. 2) I wanted to let others jump in and contribute to it so it was communally owned.
I personally feel its the right way to go and there is a lot of infrastructure already in place. There are still lots of gaps to be filled in, as I'm sure we'll see as we work on replacing the existing docs. For one, datatypes are not documented with this process yet.
Right now the setproxy doco is generated and looks a bit different from the
hand carved manual pages. We probably want a consistent look in the manual
and perhaps even a similar look to the rest of the Ant site. Also I want to
have some PDF generation going.
+1 - I'll try to migrate xdocs upward to the main tree and integrate it into the main build process. It can be a bit tricky because the build process needs to be running the same version of Ant that its processing to really work properly... we'll have to see how it goes.
<macrodef> could be done and would be a good idea. It would provide a way of
composing tasks into larger tasks. Peter has mentioned a system to provide
task default attribute settings for standard tasks. I've thought about an
<antschema> as a companion to <antstructure>, potentially supporting the
polymorphic stuff.
I like the <macrodef> idea!
7. Bug reduction.
I'd like to go through the bugs like a dose of salts. I'd like to see all
committers getting stuck into the backlog. The things that aren't going to be
done or are unlikely in the forseeable future (e.g.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3807) could go, IMHO.
Voting for bugs will help us to prioritise them.
No promises, but I'll take a look at what bugs exist in my domains of fancy and see if there are any I can knock out.
Erik
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
