Kevin, you are correct, the only way to get this going is to have people
work on it. Assigning people tasks is a great way, but sometimes a little
challenging for projects of this nature. I'm a little hesitant to do as
everyone here is a limited volunteer. I was hoping that with a nightly build
server it is much easier to see what a release build would look like.
Basically the nightly builds (run if there are changes for the day) should
reflect what we would put out for a release. That way we can just check
stuff in to cvs and everyone can look at the same results.

I think we have gone through this nsis/msi discussion before. I'd lean
towards a MSI installer rather than a nsis installer. We now have a MSI
installer task in NAntContrib that seems to do all we need. I'd much rather
see a nant installer using that tech. Please see this post for a summary of
what was done.
http://www.mail-archive.com/[email protected]/msg0
0034.html (I also have some private email with more details if you are
interested)

In the NAntContrib project there is a build target that generates this. It
creates an install for NAnt, NAntContrib and the extra tools. It is very
cool, and should do what we need, and more. (BTW. Thanks Jayme, your
contributions are much appreciated)

HTHs,
Scott

----- Original Message -----
From: "Miller, Kevin" <[EMAIL PROTECTED]>
To: "Griffin Caprio" <[EMAIL PROTECTED]>; "Scott Hernandez"
<[EMAIL PROTECTED]>; "Mark Griffiths" <[EMAIL PROTECTED]>; "Jeffrey McManus"
<[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Wednesday, February 05, 2003 12:39 PM
Subject: RE: [nant-dev] Next release


> >What can we do as a community to ensure that this
> >doesn't happen again?
>
> I would say the best solution is for people to jump on board and volunteer
one of the tasks Scott outlined...
>
> 1.  Looks like Scott volunteered himself.
> 2.  If someone feels excited about this one
> 3.  If I may it would be good for someone to crawl the list archive and
extract a FAQ.
> 4.  Agreed but isn't Jeffrey working on this?
>
> ****
> 5.  Bundle task - I will volunteer to make a NSIS -
http://www.nullsoft.com/free/nsis/ - step in the build process. I have done
this already for my local nant build.
> ****
>
> Scott Wrote:
>
> 1.) I've got to make some quick changes so that we don't force the 1.0
> framework, but that is pretty small.
> 2.) ChangeLog (We need to build this by hand from the cvs changes. This is
> not a very attractive option, but I don't know of another way). If anyone
> knows how to get a list of changes from cvs since the last release (by tag
> or date) please let me know. Right now the I can do it, but it is about
90%
> duplicate text and very hard to read.
> 3.) Readme and installation docs. There have been a lot of changes since
the
> last release. I want users to see that and not flood the list with
questions
> we can answer upfront. :)
> 4.) The website, userdocs, and references; these can wait as we are still
a
> pre-1.0 release.
>
> We have a MSI task in NAntContrib that I want to use, but for now we will
> continue to distribute as a Zip file. Maybe after we release NAntContrib
we
> can do a combined MSI distributions with tools and all.



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