#532 tag major xslt releases so specific versions can be identified

[Elli Mylonas]

Major releases of the TEI's XSL stylesheets can break other projects' workflows that rely on them. This has happened to Epidoc, for ex.

Would it be possible to use tags to identify releases in the github repo, so a project could point to an older release instead of the latest.

This would make it easier for other projects to update when they have tested. Or to not update at all.

[Sebastian Rahtz]

this ought to an issue on the TEI Stylesheets Github repo.

I'd happily do tags, if I knew how. Is it easy?

More importantly, I was expecting people to pick up releases from the published places (i.e. Debian package, SF, etc), not from following G'hub. If you track the bleeding edge stuff, it might well not be working at any given point.

Most importantly, though, it would be really helpful to get feedback if/when the stylesheets break some other project, so that I put in ever more safeguards and tests. If I knew what others were doing, I'd know what pitfalls to avoid.

[BODARD Gabriel]

Well, the person who set-up the EpiDoc Guidelines generation process for us (a certain Mr Rahtz) had us include the TEI XSLT in the SVN process. (I'm not sure how else we'd include it so that it checks out for all new users, other than pointing to an online version which might prove to be slow/unavailable on run-time.)

I know how to do tags in SVN (just make a svn:copy of the directory in /tags). I presume it's similar in Git?

[Sebastian Rahtz]

I just did a new release, 7.26.0, and i believe I tagged it. how does one tell?

[Hugh A. Cayless]

I don't see any tags on Github. You have to explicitly push them. See
"Pushing Tags" on https://help.github.com/articles/pushing-to-a-remote/

On Fri, Nov 7, 2014 at 7:46 AM, Sebastian Rahtz rahtz@users.sf.net wrote:

I just did a new release, 7.26.0, and i believe I tagged it. how does one
tell?

---

• [feature-requests:#532]
  http://sourceforge.net/p/tei/feature-requests/532 tag major xslt releases
  so specific versions can be identified*

Status: open
Group: AMBER
Created: Fri Oct 31, 2014 06:04 PM UTC by Elli Mylonas
Last Updated: Thu Nov 06, 2014 05:34 PM UTC
Owner: Sebastian Rahtz

Major releases of the TEI's XSL stylesheets can break other projects'
workflows that rely on them. This has happened to Epidoc, for ex.

Would it be possible to use tags to identify releases in the github repo,
so a project could point to an older release instead of the latest.

This would make it easier for other projects to update when they have
tested. Or to not update at all.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/tei/feature-requests/532/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

[Sebastian Rahtz]

On 7 Nov 2014, at 14:41, Hugh A. Cayless hcayless@users.sf.net wrote:

I don't see any tags on Github. You have to explicitly push them. See
"Pushing Tags" on https://help.github.com/articles/pushing-to-a-remote/

I did

git push origin —tags

did that have any effect?

--
Sebastian Rahtz
Chief Data Architect
University of Oxford IT Services
13 Banbury Road, Oxford OX2 6NN. Phone +44 1865 283431

[Elli Mylonas]

Hugh also opened a ticket on this on github
https://github.com/TEIC/Stylesheets/issues/61

[Sebastian Rahtz]

closing this, as its hand, and is also on G'hub