[nant-dev] Bug tracking status

2006-05-16 Thread Gary Feldman

There are currently no open P9 bugs.  Only two bugs were submitted in
the first half of May, nine in all of April.  Of the nine in April, two
were duplicates, one had already been fixed, one was user error, one has
been fixed, two are pending more information.  I've marked one of them
postponed, because I don't believe it's needed for 0.85.  Only one of
the two May bugs looks like it needs to be addressed (1481841 exec
task's commandline and arg eat = signs
https://sourceforge.net/tracker/index.php?func=detailaid=1481841group_id=31650atid=402868 


), but I suspect that arg value... can be made to work.

In my opinion, that's enough to close out 0.85 and release it.  Granted,
I'm exploiting the fact that the default priority is 5, not 9.
Nevertheless, 0.85 is still a pre-1.0 version number and there's more
noise about getting a new release out than fixing any particular bug.
Furthermore, a release is really necessary at this time to maintain
credibility against MSbuild.

Therefore, I propose that the next full build be declared the 0.85 final
release, and that 0.86 be opened.  The only exception to this would be
any identified showstoppers, where showstopper is defined as:  a) it
affects most NAnt users; b) there is no workaround; and either c1) it
prevents using NAnt for its primary purpose (building .Net projects) or
c2) the fix would break many existing build files.  I can even be
convinced to remove c2, but I doubt that's an issue.

Gary





---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Bug tracking status

2006-05-16 Thread Gert Driesen
 

 -Original Message-
 From: [EMAIL PROTECTED] 
 [mailto:[EMAIL PROTECTED] On 
 Behalf Of Gary Feldman
 Sent: dinsdag 16 mei 2006 17:32
 To: nant-developers@lists.sourceforge.net
 Subject: [nant-dev] Bug tracking status
 
 There are currently no open P9 bugs.  Only two bugs were submitted in
 the first half of May, nine in all of April.  Of the nine in 
 April, two
 were duplicates, one had already been fixed, one was user 
 error, one has
 been fixed, two are pending more information.  I've marked one of them
 postponed, because I don't believe it's needed for 0.85.  Only one of
 the two May bugs looks like it needs to be addressed (1481841 exec
 task's commandline and arg eat = signs
 https://sourceforge.net/tracker/index.php?func=detailaid=148
 1841group_id=31650atid=402868 
 
 ), but I suspect that arg value... can be made to work.

Gary, were you able to reproduce this issue ? It's working fine here.

I think that the issue described by the submitter is due to the way command
line arguments for batch files are processed, and as such this has nothing
to do with NAnt itself.

 In my opinion, that's enough to close out 0.85 and release 
 it.  Granted,
 I'm exploiting the fact that the default priority is 5, not 9.
 Nevertheless, 0.85 is still a pre-1.0 version number and there's more
 noise about getting a new release out than fixing any particular bug.
 Furthermore, a release is really necessary at this time to maintain
 credibility against MSbuild.
 
 Therefore, I propose that the next full build be declared the 
 0.85 final
 release, and that 0.86 be opened.  The only exception to this would be
 any identified showstoppers, where showstopper is defined as:  a) it
 affects most NAnt users; b) there is no workaround; and either c1) it
 prevents using NAnt for its primary purpose (building .Net 
 projects) or
 c2) the fix would break many existing build files.  I can even be
 convinced to remove c2, but I doubt that's an issue.

I'd still prefer to have one more release candidate before we ship a new
final release.

I hope to have time in the next two weeks, but I realise I've said that
before :(

We've also lost the instructions for our release procedure when the Wiki was
killed (pfff), so it'll take a little longer than usually.

Gert



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


Re: [nant-dev] Bug tracking status

2006-05-16 Thread Gary Feldman

Gert Driesen wrote:




Gary, were you able to reproduce this issue ? It's working fine here.

I think that the issue described by the submitter is due to the way command
line arguments for batch files are processed, and as such this has nothing
to do with NAnt itself.
 


I didn't try, because my intuition agrees with your analysis.


I'd still prefer to have one more release candidate before we ship a new
final release.

 

OK, but let's pick a time frame for the interval between that and the 
real release, along with a policy of no checkins (on the trunk) during 
that period except for showstoppers.


Gary




---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers


RE: [nant-dev] Bug tracking status

2006-05-16 Thread Martin Aliger
Great! I think NAnt needs new release badly. The fact, it has no stable
release for year or so hurt the project, imho.

Next thing we should do is VS2005 projects. I prefer msbuild integration
way, but its 0.86 or rather 0.9 matter!

btw: it'd be better to release atleast 2 or 4 version a year, even that not
so well tested, perhaps. We could always rerelease patched version.

Regards,
Martin Aliger
 
 In my opinion, that's enough to close out 0.85 and release 
 it.  Granted, I'm exploiting the fact that the default 
 priority is 5, not 9.
 Nevertheless, 0.85 is still a pre-1.0 version number and 
 there's more noise about getting a new release out than 
 fixing any particular bug.
 Furthermore, a release is really necessary at this time to 
 maintain credibility against MSbuild.
 
 Therefore, I propose that the next full build be declared the 
 0.85 final release, and that 0.86 be opened.  The only 
 exception to this would be any identified showstoppers, where 
 showstopper is defined as:  a) it affects most NAnt users; b) 
 there is no workaround; and either c1) it prevents using NAnt 
 for its primary purpose (building .Net projects) or
 c2) the fix would break many existing build files.  I can 
 even be convinced to remove c2, but I doubt that's an issue.
 
 Gary



---
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
nant-developers mailing list
nant-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-developers