Yep, I did give the Web site a once-over to add some documentation to clear up some conceptual disconnects that I had when I was learning the tool. And I'll be happy to put in more time to deal with any other documentation issues that need to be dealt with for an 0.8 release -- I'd like to hear a consensus from developers about priorities in this area. (Two examples I'll volunteer -- Adding new information for developers who are new to the concept of build tools: high priority. Converting existing documentation into XML: low priority. That kind of thing.)
I have just been looking for a block of time to figure out how to do the necessary CVS submit (I'm accustomed to Perforce and fecund SourceSave but figuring out CVS shouldn't be hard, just need to find a block of time). One of the things that I've found is useful when I notice a project dragging along is to give myself a deadline. Just a thought. -J. --- "Miller, Kevin" <[EMAIL PROTECTED]> wrote: > >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. __________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ------------------------------------------------------- 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
