Re: [tei-council] Release

Ok. I’ve done the oxygen-tei release 4.0.0. I still don’t understand how the script can be expected to run unless you do it somehow between the time when you run tei-install.sh --install and --makecurrent. http://www.tei-c.org/release/oxygen http://www.tei-c.org/release/oxygen is a symlink to /projects/tei/web/Vault/P5/current/oxygen and when you run tei-install.sh no oxygen directory gets put in place in release/. Was there once one in http://bits.nsms.ox.ac.uk:8080/job/TEIP5/lastSuccessfulBuild/artifact/P5/rel... http://bits.nsms.ox.ac.uk:8080/job/TEIP5/lastSuccessfulBuild/artifact/P5/rel... Without the oxygen directory, the symlink goes nowhere, the ant script can’t download the updateSite.oxygen file, and it cannot continue. Presumably this used to work…we’ll need to fix it one way or the other before the next release.

On Oct 16, 2015, at 12:26 , Hugh Cayless wrote:

FWIW, the script still uploads to tei-oxygen: https://github.com/TEIC/oxygen-tei/blob/master/oxygen-tei/build.xml#L12 https://github.com/TEIC/oxygen-tei/blob/master/oxygen-tei/build.xml#L12

On Fri, Oct 16, 2015 at 12:20 PM, Hugh Cayless mailto:philomousos@gmail.com> wrote: Ah, the bloody tei-oxygen vs. oxygen-tei thing. Oy gevalt.

On Fri, Oct 16, 2015 at 12:18 PM, Hugh Cayless mailto:philomousos@gmail.com> wrote: It's not destroyed, but it's not linked where the build script expects it to be anymore. I managed to build it by pointing it at the last one in the vault, but then stopped because what it thinks was the last release (3.0.0) doesn't agree with what I see at http://sourceforge.net/projects/tei/files/tei-oxygen/ http://sourceforge.net/projects/tei/files/tei-oxygen/. So should we be doing 3.0.0 or 4.0.0?

On Fri, Oct 16, 2015 at 12:11 PM, Martin Holmes mailto:mholmes@uvic.ca> wrote: The Oxygen update file shouldn't be destroyed during the release process of P5. Did that happen somehow?

Cheers, Martin

On 2015-10-16 02:38 PM, Hugh Cayless wrote: Ok, looking at the ant build.xml file, it seems like the oxygen plugin depends on getting the *previous* release’s updateSite.oxygen file and building a new one, which is fine, but how is that supposed to happen *after* you’ve done the rest of the release, when it isn’t there anymore? But the plugin (obviously) also depends on the rest of the release having been done, so it can download the artifacts.

I’m badly confused now.

On Oct 16, 2015, at 8:19 , Hugh Cayless mailto:philomousos@gmail.com> wrote:

Dear All,

The 2.9.1 release is out, except for the Oxygen plugin, which I can’t build, because it relies on downloading a file that isn’t there: http://www.tei-c.org/release/oxygen/updateSite.oxygen http://www.tei-c.org/release/oxygen/updateSite.oxygen <http://www.tei-c.org/release/oxygen/updateSite.oxygen http://www.tei-c.org/release/oxygen/updateSite.oxygen> and which the release documentation doesn’t tell me how to put there. There’s a copy in https://github.com/TEIC/TEI/blob/master/P5/updateSite.oxygen https://github.com/TEIC/TEI/blob/master/P5/updateSite.oxygen <https://github.com/TEIC/TEI/blob/master/P5/updateSite.oxygen https://github.com/TEIC/TEI/blob/master/P5/updateSite.oxygen> that looks outdated, but maybe that doesn’t matter. Anyway, can one of you kind people who know how this stuff works help? I’m inclined to hold off on announcing until the plugin is ready, but maybe that’s overly cautious?

Thanks, Hugh

-- tei-council mailing list tei-council@lists.tei-c.org mailto:tei-council@lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council http://lists.lists.tei-c.org/mailman/listinfo/tei-council

PLEASE NOTE: postings to this list are publicly archived