RE: [nant-dev] Next release

2003-02-10 Thread Cort Schaefer
This is what I use

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]] On Behalf Of Scott
Hernandez
Sent: Wednesday, February 05, 2003 10:48 AM
To: Mark Griffiths
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] Next release

Docs, Docs, Docs... Okay, here is what I see.

The code is very stable.

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.

- Original Message -
From: Mark Griffiths [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 8:15 AM
Subject: [nant-dev] Next release



 Are you any closer to releasing a new version 'proper'?  The 0.7.9
release
 is dated 11-jun-2002 - nearly 8 months ago.  Is there anything in
particular
 that is holding the release up?  Anything that I could lend a hand to?

 Cheers
 -MG



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





cvs2cl.pl
Description: Binary data


Re: [nant-dev] Next release

2003-02-10 Thread Gert Driesen
Would it be possible to include support for building .NET Compact Framework
assemblies in the release ?

You should also be able to choose which .NET runtime you want to compile
against.  Is this currently possible ?

Thanks,

Gert

- Original Message - 
From: Cort Schaefer [EMAIL PROTECTED]
To: 'Scott Hernandez' [EMAIL PROTECTED]; 'Mark Griffiths'
[EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 11:06 PM
Subject: RE: [nant-dev] Next release


 This is what I use

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]] On Behalf Of Scott
 Hernandez
 Sent: Wednesday, February 05, 2003 10:48 AM
 To: Mark Griffiths
 Cc: [EMAIL PROTECTED]
 Subject: Re: [nant-dev] Next release

 Docs, Docs, Docs... Okay, here is what I see.

 The code is very stable.

 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.

 - Original Message -
 From: Mark Griffiths [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Wednesday, February 05, 2003 8:15 AM
 Subject: [nant-dev] Next release


 
  Are you any closer to releasing a new version 'proper'?  The 0.7.9
 release
  is dated 11-jun-2002 - nearly 8 months ago.  Is there anything in
 particular
  that is holding the release up?  Anything that I could lend a hand to?
 
  Cheers
  -MG
 
 
 
  ---
  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






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



Re: [nant-dev] Next release

2003-02-06 Thread Sansone, Aaron
I agree with Dave, documentation needs to be addressed.  I really like the Wiki
idea.  We used a Wiki for documentation on my last project with good success.
Our customer resisted it at first our original idea was to get the users to help
with the documentation by editing the pages.  It was accepted as a documentation
medium when we showed that we could have an admin user that allowed us to edit
the documentation and not allow the users to alter it.  We gave our user base a
separate forum for adding notes, requests and communication amongst
themselves.

shameless_plug
I'd be willing to take a look at deploying a wiki to my NCode Sourceforge
project to see if it works.  NCode is a VS.Net IDE Add-In that does code
completion from live templates (just like IntelliJ if anyone has used that).
urlncode.sourceforge.net/url
/shameless_plug

-Aaron

-Original Message-
Message: 9
Date: Thu,  6 Feb 2003 07:44:23 -0500
From: Dave Sanders [EMAIL PROTECTED]
...
Documentation.

Specifically I've had to spend a lot of time just playing with it and seeing
what it does. 
...

Have you considered hosting a Wiki for keeping and maintaining documentation? 
Even if you kept it hidden away for the developers list, and published out
static files as the documentation - it would be a quick and easy way for all of
us to contribute little snippets of information without any one person or group
of people having to write full documentation.



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



Re: [nant-dev] Next release

2003-02-06 Thread Dave Sanders
Quoting Tomas Restrepo [EMAIL PROTECTED]:
 That sounds like a great idea. Scott, what do you think? If there's any
 problem with getting it on the sourceforge servers, I'd be willing to share
 some space on my hosting (provided we find a wiki we can run there).

I'm using PureEnergy hosting for mine: http://www.purenrg.com/.  $6 a month,
runs on linux and has a lot of good features.  This is where I've set up TWiki
for my site.

If you want a microsoft based wiki, you can go look here
http://www.openwiki.org/ - not as full featured as others, but it works well.

Or, find a huge lists of wiki's here: http://www.purenrg.com/ - the Original
Ward Cunningham wiki.  There are some dotNET ones, but I haven't had good luck
with them - mainly they don't have a lot of features, or they aren't done and
aren't showing progress.

D


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



Re: [nant-dev] Next release

2003-02-06 Thread Ian MacLean
Sansone, Aaron wrote:



shameless_plug
I'd be willing to take a look at deploying a wiki to my NCode Sourceforge
project to see if it works.  NCode is a VS.Net IDE Add-In that does code
completion from live templates (just like IntelliJ if anyone has used that).
urlncode.sourceforge.net/url
/shameless_plug

 

looks good Aaron. Did you copy the NAnt home page ? It still says NCode 
- A .NET Build Tool in the title :)

Ian


-Original Message-
Message: 9
Date: Thu,  6 Feb 2003 07:44:23 -0500
From: Dave Sanders [EMAIL PROTECTED]
...
Documentation.

Specifically I've had to spend a lot of time just playing with it and seeing
what it does. 
...

Have you considered hosting a Wiki for keeping and maintaining documentation? 
Even if you kept it hidden away for the developers list, and published out
static files as the documentation - it would be a quick and easy way for all of
us to contribute little snippets of information without any one person or group
of people having to write full documentation.



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



[nant-dev] Next release

2003-02-05 Thread Mark Griffiths

Are you any closer to releasing a new version 'proper'?  The 0.7.9 release
is dated 11-jun-2002 - nearly 8 months ago.  Is there anything in particular
that is holding the release up?  Anything that I could lend a hand to?

Cheers
-MG



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



RE: [nant-dev] Next release

2003-02-05 Thread Turpin, Jay
I am willing to pitch in as well. I would like to get a new release of
Nant and NAntContrib so that when they are downloaded, both will build
properly without hand-holding.

Regards,
Jay Turpin
Intel Corporation
The only difference between a problem and a solution is that people
understand the solution. - Charles Kettering


-Original Message-
From: Mark Griffiths [mailto:[EMAIL PROTECTED]] 
Sent: Wednesday, February 05, 2003 9:16 AM
To: [EMAIL PROTECTED]
Subject: [nant-dev] Next release



Are you any closer to releasing a new version 'proper'?  The 0.7.9
release
is dated 11-jun-2002 - nearly 8 months ago.  Is there anything in
particular
that is holding the release up?  Anything that I could lend a hand to?

Cheers
-MG



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



Re: [nant-dev] Next release

2003-02-05 Thread Scott Hernandez
Docs, Docs, Docs... Okay, here is what I see.

The code is very stable.

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.

- Original Message -
From: Mark Griffiths [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Wednesday, February 05, 2003 8:15 AM
Subject: [nant-dev] Next release



 Are you any closer to releasing a new version 'proper'?  The 0.7.9 release
 is dated 11-jun-2002 - nearly 8 months ago.  Is there anything in
particular
 that is holding the release up?  Anything that I could lend a hand to?

 Cheers
 -MG



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



Re: [nant-dev] Next release

2003-02-05 Thread Tomas Restrepo


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


I think part of the problem is that it seems Scott is the only one of the
project admins that has been around for the past few weeks (months?)
devoting any real time to nant, and he's the one in the best position to do
anything (and probably the only one with permisions to actually do the final
release).

Personally, I'm a little busy now, so that's why I've only contributed
marginally lately, but if I can do anything to speed up the process, let me
know.
Also, consider that last time the topic came up, I said the NUnit2 support
stuff was a showstopper, and I've since fixed it (what could be fixed
without changing NUnit itself).

--
Tomas Restrepo
[EMAIL PROTECTED]



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



Re: [nant-dev] Next release

2003-02-05 Thread Scott Hernandez
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/nantcontrib-developer@lists.sourceforge.net/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



RE: [nant-dev] Next release

2003-02-05 Thread Miller, Kevin
I was really calling for volunteers in areas of expertise and volunteering myself to 
set an example. Of course I took one of the easy/optional tasks as I am lazy. 

I am cool with the MSI Task. I will take a look at learning how it works. Of course 
this is not a gate to a release. 

Kevin

-Original Message-
From: Scott Hernandez [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 05, 2003 3:52 PM
To: Miller, Kevin; Griffin Caprio; Mark Griffiths; Jeffrey McManus
Cc: [EMAIL PROTECTED]
Subject: Re: [nant-dev] Next release


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/nantcontrib-developer@lists.sourceforge.net/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



RE: [nant-dev] Next release - and Nunit2

2003-02-05 Thread Arnoldus, Michael
About the next release - I'm all for releasing what we have right now.

 Also, consider that last time the topic came up, I said the NUnit2 support
 stuff was a showstopper, and I've since fixed it (what could be fixed
 without changing NUnit itself).

I agree nunit2 is not a showstopper - but as I have said before I do not
think 
the Nunit2 task works as it should, since it will report failure on test
assemblies
the nuint2 testunner can run without any failures (current directory issue).
I have
working examples of this. 

Tomas - it it something you want me to work with, or do you disagree with
the intention
that the Nunit2 task should test assemblies the same way the Nunit2
Testrunner does - or ...

And again - this is not a tangent that should prevent anyone from doing a
release ... :-)

Enjoy,

Michael Arnoldus

--
Tomas Restrepo
[EMAIL PROTECTED]



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