Hi,
>
> > Hi All,
> >
> > So I am not sure this is going to capture everyone's
> interest but on the
> > other hand it is a "first attempt" and I don't really
> expect it to :-).
> > I have uploaded an example of the changelog here:
> >
> >
> http://nant.sourceforge.net/tmp/changelog_2003-12-26_to_2004-9-14.html
>
> It looks good ... if you're color-blind (lol) ... I don't
> really like the
> blue bar and grey background, but those are details ...
>
> I'm also not sure if we should put the NAnt logo on the
> change log as that
> logo will not be available for users without internet connection.
>
I agree about the colour, I spent some time fiddling with the header but
figured that the rest was "good enough" for a demo :-). The green and
orange don't exactly mix well but the green and white might work. I
think it would be alright to leave the logo and just make it relative to
the rest of the docs.
> >
> > Instead of using the local property file I went with the
> last release
> > date of NAnt, in this case 2003/12/26. I would like to hear what
> > everyone else thinks but this seemed to make sense that we
> would want to
> > capture all changes from the last release date.
>
> I guess it would be nice to have both a change log doc doc
> with only the
> changes since the last nightly build (which we would only
> include with the
> nightly builds) and one with changes since the last release
> (which we would
> include with betas/releases, and perhaps also with nightly builds).
>
Okay, I was kind of hoping to avoid both and just let the potential
downloader lookup the dates between the nightly builds but it sounds
like the preference is to automate that. This will probably mean
dumping the last nightly build date (last known build) to a file
somewhere and just reading from that. I am not sure if it makes more
sense to store this on sf.net somewhere or to check it into cvs? If
there are no objections I would rather go the cvs route.
> >
> > Just a couple of more notes: I have also slightly modified the
> > changelog.xls that comes with ant to make it more NAnt-ish :-), this
> > will have to be checked in but probably not distributed?
>
> yeah, guess so... should we store it in the "doc" directory
> or should we
> also have a "etc" directory (like, for example, Ant has) ?
I am leaning towards the "etc" directory, just because it is not exactly
documentation.
> > The output is
> > just going to the ${build.dir}/doc folder, does that seem
> reasonable or
> > is there a more appropriate location?
>
> For releases/betas, I think I would prefer storing it in the
> root directory
> ...
>
> For nightly builds, I think we could store the change log
> containing all
> changes since the last release in the root directory of both
> the binary and
> the source distribution. The change log containing the
> changes since the
> last nightly build should perhaps only be available in the download
> directory of that nightly build.
>
> What do you think ?
>
So we would package the changelog in the binary and source distributions
and then put the changes since the last nightly on the website? I think
that is a good idea, it will give someone an idea if they even want to
download the latest nightly if they are not monitoring the lists
closely.
Cheers,
Clayton
-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
