Path: csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!news.glorb.com!news-out.octanews.net!indigo.octanews.net!auth.brown.octanews.com.POSTED!not-for-mail From: Paul Rubin Newsgroups: comp.lang.forth Subject: Re: Complexity References: <30126800.1344.1332858395156.JavaMail.geo-discussion-forums@ynnk21> <7x62do94jc.fsf@ruckus.brouhaha.com> <0-ydndWHCKzE2O7SnZ2dnUVZ_jydnZ2d@supernews.com> <7xbonasmz9.fsf@ruckus.brouhaha.com> <9IidnbKbIq7H6eTSnZ2dnUVZ_tGdnZ2d@supernews.com> <7x62dhejfv.fsf@ruckus.brouhaha.com> <7x398knpan.fsf@ruckus.brouhaha.com> <7xwr5qdctb.fsf@ruckus.brouhaha.com> <2012Apr9.105255@mips.complang.tuwien.ac.at> <8562dd4e-5a5e-463e-b2e0-ee2a44226bcc@y13g2000yqj.googlegroups.com> Date: Mon, 09 Apr 2012 10:17:31 -0700 Message-ID: <7xk41odduc.fsf@ruckus.brouhaha.com> Organization: Nightsong/Fort GNOX User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1 (gnu/linux) Cancel-Lock: sha1:IWpRR50z9yF/qUDEncr66XCHCZg= MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Lines: 21 NNTP-Posting-Date: 09 Apr 2012 12:17:37 CDT X-Complaints-To: abuse@octanews.net Xref: csiph.com comp.lang.forth:11047 Mark Wills writes: > Let's take a team of programmers working on a file based system. In > this scenario, the issues are *exactly* the same as a team working in > just about any contemporary language you care to mention. All that is > needed is some sort of check-in/check-out version control system, ala > Source Safe which has been around for years. You probably also want: 1. Bug tracking system 2. Build scripts (so you can go all the way from your source repo to a downloadable image for your embedded whatsit in one step) 3. Unit test framework 4. Integration test / CI framework 5. Dynamic test generators 6. static analysis tools 7. Documentation tools / tracker Fossil (fossil-scm.org) is a lightweight tool that might be enough for source control, bug tracking, and internal docs. I'm not sure what to suggest for the other stuff.