You should post a patch to this list. read up on cvs diff, use the -u
option for readibility. Your contribution is welcome.
Ian
I made a pass
through all of them, correcting spelling mistakes and
adding content here and there using my tool of choice
(which happens to be Dreamweaver, but could ha
--- Scott Hernandez <[EMAIL PROTECTED]> wrote:
> 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.
Yep, I didn't mean it seriously -- hence the smiley
after the suggestion. (Although...I'm not
n
the day. :) I just haven't gotten it done.
- Original Message -
From: "Jeffrey McManus" <[EMAIL PROTECTED]>
To: "Ian MacLean" <[EMAIL PROTECTED]>
Cc: "Scott Hernandez" <[EMAIL PROTECTED]>;
<[EMAIL PROTECTED]>
Sent: Thursday, Janu
TECTED]>
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 do
> 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.
Updating the website with documentation on features
that aren't in the latest stable build
And therein lies the problem. We *need* to update the changelog. It is way
out of date. I am personally responsible for much of it(or the lack of much
of it), but have not put the time in to fix it. At this point the code is
really not keeping us from a release. The build scripts and code are ready
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
generate
> 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 ''. How would someone get access to
>documentation on this?
The correct answer is:
Do a point release, already. The current "
--- 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
: "Jeffrey McManus" <[EMAIL PROTECTED]>
To: "Scott Hernandez" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Thursday, January 23, 2003 4:41 PM
Subject: Re: [nant-dev] documentation error
> I understand that it shouldn't be edited directly, bu
I understand that it shouldn't be edited directly, but
I think it should at least be checked in, because it
represents part of the distributable package of the
application. One objective of source code is to be
able to view, at a glance, the state of an application
(including its distributable pack
It should not be checked in. Once it is generated, it is stale and it is not
the source of documentation anyway.
Why do you want it checked into source control as html? (it should not be
edited in that form)
- Original Message -
From: "Jeffrey McManus" <[EMAIL PROTECTED]>
Sent: Thursday,
--- Scott Hernandez <[EMAIL PROTECTED]> wrote:
> Right now the "Task References" are created by NDoc
> via the userdoc target.
The product of this process doesn't seem to be getting
checked in. The net result is, when you check out the
docs from CVS, the core part of the documentation (the
tasks r
ECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, January 22, 2003 8:37 PM
Subject: Re: [nant-dev] documentation error
> I'm happy to contribute as much as I can to docs; I've
> synched everything up with CVS and I'll start looking
> at them tonight. With your permissio
I'm happy to contribute as much as I can to docs; I've
synched everything up with CVS and I'll start looking
at them tonight. With your permission, one of things
I'd like to start thinking about is a short
introductory blurb/doc that introduces the concept of
a build tool at a high level for experi
Hi Jeffrey,
It looks like this has been fixed in cvs. There is no "help/documenter"
person, but if you would like to help out, there is plenty to do :) And we
would really appreciate it.
The number one thing on my list is to convert the docs here
(http://nant.sourceforge.net/help/index.html; excl
16 matches
Mail list logo
