Hi all, I now have a fresh build script for the TEI Oxygen plugin which builds the plugin package using the latest successful builds of P5 and the Stylesheets. It will build automatically after every successful TEI P5 build (which itself is triggered by any change to P5 source or following a Stylesheets build), and will also build if its own Google Code repository changes. What this means is that we should now have a trunk build of the Oxygen TEI plugin which tracks the other changes in our codebase. Most importantly, we'll know immediately if something the Oxygen guys do in the Google code repo breaks the build, or if we do something to our own codebase which breaks it. The next stage is to set up an update file for these trunk builds, like this one: http://www.tei-c.org/release/oxygen/updateSite.oxygen to which the braver among us could subscribe, so that the plugin would always get tested steadily as we work. I think the build process should create this file, so it will probably end up being on the Jenkins server itself somewhere. If anyone is interested in testing now, the latest build is here: http://teijenkins.hcmc.uvic.ca/job/oxygen-tei/lastSuccessfulBuild/artifact/o... Our current release of this plugin is called "teioxygen..." rather than "oxygen-tei", but since the Google Code project is oxygen-tei, and there is also a TEI deb package called "tei-oxygen" which has nothing to do with this, I've taken the opportunity to name my distro like this: oxygen-tei-2.7.1a-7.30.0.zip If you think it's a good idea to carry this naming over to the release package, shout; we could modify the build-and-upload script accordingly, along with the update file, and reduce potential confusion. Cheers, Martin