From the webpage:
The fourth milestone (alpha) release of Hudson from Eclipse is now available for download and evaluation from the Eclipse Download page. This version has stabilized the final library set to be used by Hudson Core at Eclipse and introduces a new initial setup feature which is used to help the administrator correctly configure the instance. You can read more here. Note that this milestone version is intended for evaluation only and should not be used in production.
Hudson is a continuous integration (CI) tool written in Java, which runs in a servlet container, such as Apache Tomcat or the GlassFish application server. It supports SCM tools including CVS, Subversion, Git and Clearcase and can execute Apache Ant and Apache Maven based projects, as well as arbitrary shell scripts and Windows batch commands.
Although any topic map software project would benefit from Hudson as a software build tool, “continuous integration” struck me as a useful notion for the substance of topic maps as well.
Including but not necessarily involving changes in how merging would occur in some cases. For example, if additional information were added to a topic map that would change the warnings given to patients about medications, the medications may already have been dispensed.
The map isn’t “wrong,” presently, but actions need to be triggered because of prior actions registered in the topic map. Not for all prior actions but just those within a particular time window.
Assuming you have treated dispensing events for medication as topics, the addition of associations with warnings could automatically trigger relevant warnings to other patients.
Sounds like “continuous integration” may have use beyond software projects!