Re: [tei-council] A decision we have to take on oxygen-tei

Hmm, I wonder if we could follow a different route. Rather than supporting the newest oxygen versions (which are not far away from the current TEI releases) we could try to support some legacy versions. At this conference, I’ve seen (again) some oXygen 14 (even 13) installations wich refused to let people validate against the current schemas. Maybe we could stick to the 14.+ plugin (in our oxygen-tei repo) and simply put in our current schemas, supplying older oXygen installations with current TEI schemas? Peter

Am 30.10.2015 um 11:11 schrieb Lou Burnard :

I agree with Martin's recommendation. Wonderful though it is, oXygen and the oXygen folks are both, it doesn't look right for the TEI to be doing their job of keeping their customers up to date. After all, there may well be oXygen users who'd prefer the stability of known release.

On 30/10/15 09:32, Martin Holmes wrote:

...

We're faced with a rather difficult decision with regard to the oxygen-tei plugin.

The Oxygen guys have introduced a lot of new features, especially relating to CSS usage in Author mode (as far as I understand it), and they've made a point of using jTEI as one of their examples. However, their new stuff only works on Oxygen 17.1. They've put it in a branch on oxygen-tei:

https://github.com/TEIC/oxygen-tei/tree/update_oxygen_17_1

Our plugin currently works on versions going back to 15.2. If we merge these exciting new changes, then people using older versions of Oxygen will suddenly get an update that breaks or won't install (I don't know exactly what will happen). However, if we don't update, we'll be in the rather odd situation that Oxygen's release will always be more advanced than our version of our plugin, which makes our plugin sort of pointless, since the main reason for it is to exist is to enable users to get a more up-to-the-minute version of the plugin.

I'm tempted to say that it might be time to retire our "official" TEI release of the plugin entirely. We could offer a bleeding-edge preview release of the plugin, based on our dev branches, which we would us for testing and would encourage savvy users with a need to get the absolute latest-and-greatest to install; but otherwise we would just rely on Oxygen's steady release cycle to keep the majority of our users up to date. That would mean a brief lag between the time that we do a major release and Oxygen does, when users of Oxygen would have no easy way to get the latest-and-greatest P5 and Stylesheets. But it would make our lives simpler.

Cheers, Martin

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

PLEASE NOTE: postings to this list are publicly archived