John Barstow wrote:
For what it's worth, here's my opinion. I'm trying to arrange things so
releases will be less chaotic affairs, so that's my main bias in my
arguments.
------------
NAntContrib should be distributed with NAnt. That means when we have a
release, we build both and package all the binaries and source together.
The list of tasks that make up NAnt need to stabilize before 1.0. There's
too much change between releases (though more frequent releases will help
fix this). By necessity, everything else needs to go into NAntContrib.
agreed. Actually the list of tasks has been fairly stable - its been
code in the core thats been changing recently.
I think for the next release (0.8.3.xxx), we should NOT restructure the
code; it will only delay things and confuse people. Instead, we simply need
to fix the project so it builds against the current version of NAnt. Both
projects will be built and distributed together for this release.
ok fair enough. NAntContrib now builds against the latest nant cvs so
we're on the way.
The following release (0.8.4.xxx), we should do whatever restructuring is
necessary, as long as we can agree that no major refactorings are going to
take place after this. One of the reasons my company is paying for me to
work on this is because we are using the project in our production
environment; if things start breaking I know I'm the one they're going to
blame.
again good. The only re-structuring I forsee is moving some tasks from
contrib into main.
Unfortunately, the major features that get implemented between releases make
it much harder to get a deep understanding of the system; that makes it
harder to contribute to the core and everyone ends up trying to commit to
NAntContrib where everything breaks anyhow.
I know there are lots of really useful features that need to be added, but
the tasks that are in there TODAY are letting people write sophisticated,
production-quality build systems. If we can polish and document the
existing functionality, we have a solid core for
a 1.0 release, and a much better foundation for integrating changes and
tasks going forward.
Why don't we try and capture all of these features as well as all the
fixes and documentation that needs doing. Then we can start assigning
them to specific releases up to 1.0 and beyond.
-------------
As for doing my part, I am going to be writing some fairly extensive release
notes this go round. Expect a first draft in about two days. In addition,
I'm going to be putting in some more unit tests as soon as we ship
0.8.3.xxx. I'm also going to be pretty aggressive about trying to get out a
new release every month.
-------------
John C Barstow
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100006ave/direct;at.asp_061203_01/01
_______________________________________________
nant-developers mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/nant-developers
