Jeffrey McManus wrote:

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.


Having docs checked in makes sense if they are edited as html. Ours are generated. We should be updating the website regularly with the latest docs. Perhaps the nightlies should include this too. But they shouldn't be in cvs.
Ian

Maybe working backwards from m 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?

-J.

__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com


-------------------------------------------------------
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




-------------------------------------------------------
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

Reply via email to