Change Details

In old releases, the lexdata master was always used. After some necessary updates, we had to use a separate branch to avoid conflicting issues with the new updates, compared to previous releases. Moving the new branch to master, may cause some backward compatibility issues with the first releases, but this should not be a problem right now.

* Move lexdata "schemaversion_3.1" branch to master (may cause some backward compatibility issues with the first releases, but this should not be a problem right now) * Update all go repos to 1.13 (including .travis specs) * Convert all go repos to go mod Go modules https://blog.golang.org/using-go-modules Versioning (https://semver.org/)

In old* Move lexdata "schemaversion_3.1" branch to master (may cause some backward compatibility issues with the first releases, the lexdata master was always used. After some necessary updates, we had to use a separate branch to avoid conflicting issues with the new updates, compared to previous releases.but this should not be a problem right now) * Update all go repos to 1.13 (including .travis specs) * Convert all go repos to go mod Moving the new branch to master, may cause some backward compatibility issues with the first releases, but this should not be a problem right now.Go modules https://blog.golang.org/using-go-modules Versioning (https://semver.org/)