My $.02 I think it is a very good idea to include nAntContrib project with the nAnt release. I depend on a lot of tasks in nAntContrib and therefore have a difficult time when nAnt releases a new version. I have to figure out if the existing nAntContrib task will work or not and then try to build them...which is a rather difficult task at times.
It might be a difficult task to update nAntContrib and include it, but I think it needs to be done sooner than later. My suggestion for including the nAntContrib project would just to drop all the dll's generated into the nant bin directory. Creating a separate directory for those dlls wouldn't make sense to me. I agree that <version> task should be moved into the core, but if we always release nAntContrib with nAnt, then this might be a moot point. I think that is a very important part of the build process. I know our project has struggled with assembly version numbering problems. I don't think that it was in this post, but someone else suggested that after a release, increment the build number...I agree with that. This is exactly how I do builds on my project. 0.8.3.<increasing build number> release 0.8.3 is actually 0.8.3.59 0.8.4.0 is the next build and so forth. Jason -----Original Message----- From: John Barstow [mailto:[EMAIL PROTECTED] Sent: Thursday, June 26, 2003 3:57 PM To: 'Gert Driesen'; 'Nant-Developers (E-mail)' Cc: 'Ian MacLean' Subject: RE: Upcoming 0.8.4? release (was RE: [nant-dev] FW: Upcoming 0.8.3 release) Lots of commentary last night. Here are my responses in no particular order. > I would still like to get a few things in the 0.8.3 release : upgrade to a > new version of #cvslib, perhaps upgrade to a yet-to-be-released version of > log4net (which now uses the same assembly name for all framework versions) > and perhaps also some fixes for NAnt on Mono ... I'm using the release process documented on the Wiki. (http://nant.sourceforge.net/wiki/index.php/ReleaseProcess) As part of the release process (step 2), I'll be pulling and testing the most recent released versions of any products NAnt relies on. I'll incorporate a list of any upgrades in the release and install notes (after running it by the mailing list first, of course). > Mono 0.25 will probable soon be released, should we hold off on 0.8.3 until > we've been able to test the current code on that release (on both linux and > windows) ? My criteria for a release at this point is that all unit tests pass on Windows using both frameworks; if we need Mono 0.25 to pass all unit tests on Linux then we can do a point release when that runtime ships. We will probably need to write more extensive unit tests, of course. > I never had any issues with these tests, can you possible debug the tests to > see what's actually happening ? My first order of business after replying to everyone. > Is it alright to do a couple of pre-0.8.3 builds before the real one (at > least one)? In theory, if all the unit tests are passing, there should be no need for a prerelease. I'd like to move to doing regular point releases, especially since I can dedicate more than weekends to this. In practice, we'll definitely do at a beta release first, followed by the real release. I hope we'll be able to create a CVS branch for the release; that way we can address bugs on the branch (followed by a point release) and continue the regular development on the main branch. I can create the branch in my local Subversion repository if we don't want to introduce CVS branches at this stage. > yep we *should* - it would be nice to have that build number > auto-increment as part of the nightly build as well. We might want to consider using the <version> task from NAntContrib (and maybe moving that task into the core, since all assemblies need to be versioned somehow). > I'll set a fixed version in src/CommonAssemblyInfo.cs in a moment (eg. > 0.8.3.05000) . What you create the release version, you could actually > increase the revision number a little (eg. 0.8.3.05010). This is very reasonable. I think if we're already on 0.8.3 in source it makes sense to update the version number to 0.8.4 for the actual release. The pre-release will be 0.8.3.xxx per your suggestion if there is agreement. > I hope you're not gonna use the same machine to build the 0.8.3 release, as > NAnt is still built using the .NET Framework 1.0 In theory anything built on 1.1 will run with the 1.0 runtime if you set the appropriate config flags. I'd actually like to test that with the pre-release, and if it works it won't matter which runtime we build it with. I definitely will be doing some testing around configuration management; the current release fails to build projects on a 1.1 box without some tinkering. Finally, I'd very much like to include NAntContrib as part of the next release. Does anyone have any ideas about how we should include it? Personally, I have no problem just sticking it in nant\bin, but I imagine that's not good for everyone. John C Barstow ------------------------------------------------------- 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 ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
