On 10/11/15 17:04, Martin Holmes wrote:
It works with 15.2 and above. Or at least, we claim it does. :-) We have no testing for that in place.
Precisely my point... I know people on version 14.
My question then is: are we really doing much good? Oxygen releases about twice a year, and so do we; there will be periods of two to three months when we're ahead of Oxygen, but not much more than that.
But in order to benefit from that, then users must purchase a new version of oXygen. What I'm suggesting allows users to _stay_ with their current version of oXygen as long as oXygen don't make another backwards non-compatible change. i.e. a user now reluctantly convinces his department to allow him to update to 17.1 and then can stay on 17.1 but get new versions of the TEI and Stylesheets until they make some similar change in a few years. The users I'm thinking about are not the bleeding edge, but those who can figure out the instructions to set up the auto-update of the framework, but otherwise would have to buy a new version of oXygen to get a new TEI in the way they use it. I think if we stop offering this then there will be a larger number of users who stick with significantly outdated versions of the TEI.
If our objective is to support people who absolutely must have the bleeding edge, then I think our bleeding edge plugin is actually more useful; it lets people test development versions of P5 and the Stylesheets, and in testing, they help us. If we promote it as exactly that (and provide instructions for switching back to the main framework distributed with Oxygen, I think we'd be providing something interesting and useful all round.
I'm not talking about the bleeding edge.
Except that in order to do that, they would have to keep updating their Oxygen; and if they do that, they get a relatively recent one anyway, surely?
Yes, but then won't have money to continually update again and again. So if we can offer them a way to update their framework without updating their oXygen, then it is beneficial.
If you can keep your Oxygen 16 around, that would be a good test case. The next question would be: what do we test, and how do we test it?
Actually, thinking about it, don't we have these all packaged up as debian packages? Or did we only keep the most recent ones? -James -- Dr James Cummings, James.Cummings@it.ox.ac.uk Academic IT Services, University of Oxford