<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 15, 2017 at 4:31 PM, Stephan Oepen <span dir="ltr"><<a href="mailto:oe@ifi.uio.no" target="_blank">oe@ifi.uio.no</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">hi mike,<br> <span class="gmail-"><br> > We're wondering if anyone has good strategies (implemented in software,<br> > described in documentation, or otherwise) for ensuring accurate versions?<br> <br> </span>in the days of hosting the ERG in CVS, we had a so-called commit hook<br> to force-update the revision on ‘Version.lisp’ whenever any of the<br> grammar files were changed. this mechanism got lost when migrating to<br> SVN, but i it imagine should not be hard to re-instante. i am tempted<br> to look into that for the ERG before too long, but need to finalize a<br> manuscript first :-)<br> <br> cheers, oe<br> </blockquote></div><br></div><div class="gmail_extra">Thanks! I've actually implemented one (<a href="https://github.com/delph-in/jacy/tree/develop/utils/git-hooks">https://github.com/delph-in/jacy/tree/develop/utils/git-hooks</a>), but it must be installed by the user each time they clone (i.e. checkout) the repository, so we're afraid it wouldn't be reliable. Maybe CVS hooks could be configured to work automatically after checkout out the repo? A server-side hook could refuse a bad commit, but alas we can't install server-side scripts on GitHub (a downside to not hosting your repository on your own servers).</div><div class="gmail_extra"><br></div><div class="gmail_extra">If the process is currently manual, does the ERG have a release checklist or something to make sure some steps are not forgotten?<br clear="all"></div><div class="gmail_extra"><br>-- <br><div class="gmail_signature"><div dir="ltr">Michael Wayne Goodman<div>Ph.D. Candidate, UW Linguistics</div></div></div> </div></div>