> I haven't really given it too much though, but I don't think we should have > a very long rc period. We should really try to release versions more > frequently, without sacrificing quality ofcourse.
I was just thinking about those people who can't use nightly builds for corporate reasons, and situations where updating the nant version is not as seamless as it should be from a corporate point of view. But, ok, just a thought. > > > As well there is much feedback from users who upgraded from some 0.84 > > or more recent nightly build to the latest. Is there plan to include a > > consolidated feedback in the RC release notes ? > > If you think there's something missing from the release notes, I'd > appreciate it if you could provide a patch containing improvements. I didn't mean to offense here really, and hope I didn't. I don't know if there is something precise missing, I just had this in mind because I saw many people on the list trying to update and facing some issues (including me). I wasn't aware of the work on release notes (now I am), as I didn't see it discussed here. Anyway, I'll have a look at what I noticed on the list, and try to see if the release notes are up to date with regard to that :) cheers Thibaut ps : I've got a small nant function called is-assembly (to determine whether a file is a valid assembly or not). Is it worth contributing ? I'm using it to separate my "legacy dll" from assemblies. I know there's the get-assembly-name trick, but maybe it's worth it. Tell me what you think. ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
