Oh. It sounds so simple, but this lever of automation we do not have. It would require cvs polling, or a linux build environment on sourceforge.net. Neither of which we have. Plus it would require scp support (which is not done in NAntContrib). But please feel post a patch to support these types of changes.
We do not have nightly build, we have nightly snapshots. The difference is important. We do not build nightly, we take a snapshot of cvs. In my response to your email, which you cut below, I wrote: >I agree that the website should probably contain the latest docs of the >current cvs system, as well as the last major release. But the source So I'm saying that we need to keep a copy of the docs of the current cvs image and the last release on the website, that would be my solution for where to look. We do not have such a thing yet. The other solution is a release, which is much overdue. I really don't want to hinder you from helping, maybe so other people can comment with their opinions here. I think that you and I have very different ideas about what should be in source control. ----- Original Message ----- From: "Jeffrey McManus" <[EMAIL PROTECTED]> To: "Scott Hernandez" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Thursday, January 23, 2003 5:14 PM Subject: Re: [nant-dev] documentation error > --- Scott Hernandez <[EMAIL PROTECTED]> wrote: > > The source in cvs does represent the documentation > > at any point, not the > > other way around. What your suggesting would lead to > > ever more dissimilarity > > between a build and the docs in the system. We would > > need to check in new > > docs whenever a source file is changed! That is just > > wrong. > > If only there were some kind of automated tool to do > that... :) > > I'm accustomed to thinking of docs as a part of the > deliverable package and as such, something that should > be checked in. I'm willing to accept that not > everybody does it that way, though. > > Maybe working backwards from my original problem would > shed light on this. Let's take an example...right now > in the nightly builds there is support for a tag > called '<nunit2>'. How would someone get access to > documentation on this? ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
