The problem is that you can't build TEI-dev against Stylesheets-dev and Stylesheets-dev against TEI-dev, because that's a circle; one of them has to complete successfully before the other can go ahead. So (as Peter did) we first have to build Stylesheets-dev against something else, then use it to build TEI-dev, then set Stylesheets-dev to build against TEI-dev; and from that point on, as long as nothing breaks, we're OK. But when new release branches are set up, right on the cusp of release day, we instantly have a problem, because they need to build against each other. This happens every time. The release branches should be set up several days ahead of release day, so there's time for all this to settle down. Cheers, Martin On 2020-02-13 7:13 a.m., Syd Bauman wrote:
Yes indeedy, here we are getting clipped again! :-)
I presume, perhaps quite naievely, that dev Stylesheets should test against dev TEI, and dev TEI should build with dev Stylesheets. Furthermore that release-7.49.0 Stylesheets should test against release-3.7.0 TEI, and release-3.7.0 TEI should build with release-7.49.0 Stylesheets. But again, that may be just me forgetting some nuance of this you have explained half a dozen times, but will never sit properly in my brain because it is such a slippery mess.
I would definitely like it if and when we get Test2/ working thoroughly and can get it to be less fragile (with respect to small changes in TEI) than Test/ that we just drop Test/ and thus this becomes less of a pain. (Even if the same problem, at least it would not be so annoying.)
This is the circular build process again, then.
What version should Stylesheets-dev build against, and what version should Stylesheets-release build against?
-- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre