John,
We should .. euhm .. could ... (never say should, if there's a slight chance
that Ian is gonna read the mail .. LOL) also move to a fixed version number
for releases, now that all assemblies are built using a common
assemblyinfo.cs file.
I'll set a fixed version in
Gert Driesen wrote:
John,
We should .. euhm .. could ... (never say should, if there's a slight chance
that Ian is gonna read the mail .. LOL) also move to a fixed version number
for releases, now that all assemblies are built using a common
assemblyinfo.cs file.
I'll just ignore that part of
I'll just ignore that part of that directed at me. Yep we *should* use a
fixed version number. Thats part of the reason we moved to a common
assemblyinfo.cs file in the first place isn't it ?
It was intended as a joke, but you know that right ...
yeah - I figured.
Ian
Is it alright to do a couple of pre-0.8.3 builds before the real one (at
least one)?
I found that for the last release, people are more likely to test and
send bug reports for a pre- build than a development build.
Matt.
John Barstow wrote:
I'm hoping to do an 0.8.3 release sometime next
Matt:
Is it alright to do a couple of pre-0.8.3 builds before the real one (at
least one)?
In light of this, and Gert's request to fit more features in before
releasing, I wonder if NAnt might not benefit from doing time-boxed,
instead of feature-boxed releases. If the project were to release
After some investigation, it looks like the unit tests are failing ONLY
when run by the NAnt build file. Running the tests with nunit-console
or nunit-gui results in the unit tests passing.
To reproduce, do a clean checkout of the source, change to the newly
created nant directory, and run
After some investigation, it looks like the unit tests are failing ONLY
when run by the NAnt build file. Running the tests with nunit-console
or nunit-gui results in the unit tests passing.
To reproduce, do a clean checkout of the source, change to the newly
created nant directory, and run
Hi John,
Not everything built with framework 1.1 will work with framework 1.0,
because a lot of thing have been added to framework 1.1, it's more like
everything built with 1.0 will run with 1.1, and even then, i'm not sure if
there hasn't been downward compatibility breaking changes made in
Erv Walter wrote:
It seems kind of odd to suggest that the next version of NAnt
should be 0.8.4, doesn't it? The newest release version is 0.8.2, why
are we skipping 0.8.3?
It's mainly because the CVS version has been marked as 0.8.3 for quite some
time now, and it would be clearer to
One common practice (recommend by Microsoft gurus) is to increment your
version number immediately _after_ a release, not right before a
release. This means that you have plenty of time to debug any issues
related to that version number change. I assume that's why the version
is 0.8.3 in CVS
John Barstow wrote:
After reading through the MS notes, here's what I *think* should be
happening. I'm still trying to locate the documentation for the nant config
file so I understand all the issues.
- We should default to the 1.1 framework if installed.
- If not installed, we should default to
Ian MacLean [EMAIL PROTECTED] wrote:
Gert Driesen wrote:
John,
We should .. euhm .. could ... (never say should, if there's a slight chance
that Ian is gonna read the mail .. LOL) also move to a fixed version number
for releases, now
I am concerned about the friction NAnt users are experiencing trying to
contribute and in general use the NAntContrib tasks:
http://www.iunknown.com/000278.html
I would love to help clean up NAntContrib. I have some recent experience
from updating the StarTeam tasks. I will take a look at the
13 matches
Mail list logo
