I would like to see a consistence version and date for our releases. I think each assembly we put out, in a release, should be the same (exact) version number. Also, all files should have the same date. Maybe we can change the zip task to take an optional attribute specifying the date/time to stamp the files as they are zip'd.
SharpZipLib: We can grab a new stand-alone release (when it comes out), or just use the assembly distributed with SharpDevelop. I'd lean towards just leaving it alone until there is a new stand-alone release. But at that time, we should back out my hack from the zip task. I think we were still discussing the best way to implement the features in the looptask <foreach>. Maybe we are just waiting on the work do be done, and the changes to be committed. I would not call this a show-stopper. The nightly build should work as an RC. Maybe there are some additional files we want included in an RC? If so, feel free to change the nightly.xml file to reflect what we want. Matt, thanks for taking the lead on this release, Scott ----- Original Message ----- From: "Matthew Mastracci" <[EMAIL PROTECTED]> To: "Nant-Developers (E-mail)" <[EMAIL PROTECTED]> Sent: Wednesday, March 26, 2003 8:25 AM Subject: [nant-dev] Release 0.8.2 > Before 0.8.2 goes into release mode, are there any outstanding issues > that anyone needs addressed? Specifically: > > - Any showstopping bugs? There have made some significant changes to a > number of core classes. There's always a chance for a new bug or > regression to pop up. Is the SharpZipLib date/time bug still around? > Should we update to the latest SharpZipLib before release? > > - Any unapplied patches? Looking back on the devel list, I see that > the patch in the last few weeks was for the LoopTask. This patch is > currently waiting on modifications based on feedback on the list. > > - Any task documentation/sample code bugs? As each release brings > changes to the format of the tasks, we may find that our task > documentation becomes out-of-date. We should fix these up as soon as > possible. These are the easiest bugs to fix. :) > > I'm going to plan on putting up a release candidate build in the next > few days for those who aren't fond of building from CVS. Once that's > done, I'll call for interested parties to do testing and give feedback > on the release. If no serious problems emerge, the last release > candidate will become the final 0.8.2 release! If there are > showstoppers, however, I'll do another release candidate round until we > get to the point where we can let it loose on the world. > > Please send release comments my way ASAP, > Matt. ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
