John, Thanks for taking up this task...any further progress on releasing the first beta or release candidate?
My vote would be for one distribution package with the binaries for each .NET framework in separate directories. I don't think that we should include the documentation or source in the distribution package. We should instead, direct users to the website for documentation. I would include a readme doc that explains the basics of getting things setup (for the newbie), but again, refer to a task reference on the web. >From my perspective, if I want the source, I will just get it from SF CVS. Jason -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Gert Driesen Sent: Sunday, November 02, 2003 4:04 AM To: John C Barstow; Nant-Dev Subject: Re: [nant-dev] Criteria for next release ----- Original Message ----- From: "John C Barstow" <[EMAIL PROTECTED]> To: "Nant-Dev" <[EMAIL PROTECTED]> Sent: Sunday, November 02, 2003 5:45 AM Subject: [nant-dev] Criteria for next release > Now that I have access to an account that can post successfully to the > list, I think we should decide on the criteria for the next release. > > I propose the following: > > We ship the next release as soon as possible. There have been a lot of > bugfixes since 0.8.3. I agree we should release a new version as soon as possible ... But we should definitely have a small beta-cycle ... > > According to the TODO list, we have not yet finished the 0.8.x items. > In that case, we would want the new release to be numbered 0.8.4 instead > of 0.9.0 Sure, 0.8.4 it is ... > > We adopt the NDoc method of determining which runtime to build against. > Basically, the NDoc scripts use the <available> task to determine which > runtimes and SDKs are installed and builds against those. glad you like the NDoc build files: -) But to be honest the Ndoc build is actually more simple as it does not involve document generation (which is pretty strange for such a tool) and no automatic deployment to a website and stuff ... We could ofcourse automate all this for NAnt, but then we have to make some decisions reagarding packaging and deployment. eg. will we have one distribution package including the binaries for all supported frameworks/platforms and separate docs for each framework/platform ? The docs for which framework will be deployed to the website ? if we have separate packages for each support framework/platform, then should all of these packages include binaries, docs and sources ? Should we have binary-only distribution packages ? ............... > This would > cut down on the number of issues people have when building from source. > We should still use the -k parameter to build against specific targets. > > Do we have any tasks under active development we think a release should > wait on? Most existing tasks seem to be pretty stable at this point. The doc generation could probable do with some polishing ... We should perhaps create a small list of things to do for the 0.8.4 release in the to-do list document. > Once everyone's made decisions about the above, I'm prepared to roll the > next release. I will start work on the change log immediately. Great, thanks for taking this task upon yourself ... Gert ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
