fcbond
commented
7 years ago Sure.
Can you do that? Or if not, walk me through it.
On Tue, Nov 8, 2016 at 10:38 AM, Michael Wayne Goodman < notifications@github.com> wrote:
Since the move to Git, using the SVN revision number as an ad-hoc release number (e.g. Jacy-461) no longer makes sense. Tagged releases in Git are easy, so I request that we make a versioned release of Jacy, perhaps before any major bug-fixing push (to document the current state). A versioned release would help with reproducibility for projects that use Jacy.
The ERG has versions with rough MMYY formats (e.g. 1212, 1214), although the 1214 release didn't actually happen in 2014. If a date-based version is selected, I suggest using a standard date format (see here: http://moin.delph-in.net/GrammarVersionRfc).
E.g., we could set the version to "Jacy (2016-11-08)" and tag the commit as a release.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/delph-in/jacy/issues/33, or mute the thread https://github.com/notifications/unsubscribe-auth/ABD8xh_TynNgkT0i7aLGS-gQ_Q7OXEPMks5q8MG2gaJpZM4Ksw4c .
Francis Bond http://www3.ntu.edu.sg/home/fcbond/ Division of Linguistics and Multilingual Studies Nanyang Technological University
Since the move to Git, using the SVN revision number as an ad-hoc release number (e.g.
Jacy-461) no longer makes sense. Tagged releases in Git are easy, so I request that we make a versioned release of Jacy, perhaps before any major bug-fixing push (to document the current state). A versioned release would help with reproducibility for projects that use Jacy.The ERG has versions with rough MMYY formats (e.g. 1212, 1214), although the 1214 release didn't actually happen in 2014. If a date-based version is selected, I suggest using a standard date format (see here: http://moin.delph-in.net/GrammarVersionRfc).
E.g., we could set the version to "Jacy (2016-11-08)" and tag the commit as a release.