John, You are right - a release is due soonish.
There has been some discussion on the nant-contrib dev list about bringing that code in sync with nant-cvs.I can't seem to build the latest nant-contrib. It errors out looking for a tools folder. Futhermore, copying the prebuilt binaries to my nant directory and attempting to use the <version> or <concat> task fails; it claims 'unknown task'.
agreed - we documented what needs to be done for the release process at http://nant.sourceforge.net/wiki/index.php/ReleaseProcess. Please add anything you feel is missing to this list. Seeing as how there have only been 2 people actively committing recently its been a little hard to assign hard roles. We had been assigning a different person for each release. Matt mastracci mnaged the 0.82 release. If you want to pick up the next one that would be great.
Isn't it about time for a 0.8.3 release, BTW? 0.8.2 has some known bugs that have long sinced been fixed. --- So, here's what I think *should* happen. I'm willing to spend some time and effort to make it so IF there is agreement.
Someone needs to be a real release manager for this project. They should be rolling a release about once a month; prodding people to get all the unit tests passing, and the builds working on the run-up to release; and making sure there are real release notes.
I was also wanting to put together a list of most wanted bug fixes and feature requests so that we can start assigning features to future releases.
that makes sense. Its just a matter of keeping all that code in sync with nant cvs.
Also, I think the NAntContrib stuff should be included by default (even
if not installed in bin by default). This is important because a) a lot
of people need some of that functionality anyways and b) because it will
shake out build/dependency bugs a lot faster.
Finally, the bug database, if it exists, needs to be available from theThis is now only two clicks away - its part of the sf page but we can add a direct link. We haven't been using it to track everything but that should change. Feature requests should go here too.
home page so people know when bugs exist and have been fixed. This
saves a lot of searching through the archives.
I am willing to step up and roll a release if I can get read access toYou have my committment. I really appreciate you volunteering. What is your sf user id ?
the HEAD of source and a commitment to review and apply release-related
patches (such as documentation fixes/release notes, etc). I'll even
take a stab at writing an installer for the 0.8.4 or 0.9 release.
Ian
------------------------------------------------------- This SF.Net email is sponsored by: INetU Attention Web Developers & Consultants: Become An INetU Hosting Partner. Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission! INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
