On 08-Jun-2016, David Griffith wrote: > I've just uploaded inform-6.33-6.12.1.tar.gz to the IF Archive[1].
Thank you! > Per suggestions, I've given the release two version numbers: one for > the compiler component and one for the library component. Uhm. I'm not aware of suggestions to give *one* tarball two version strings simultaneously. Rather, I think the suggestion was to have a version scheme for each separately-released project: if it gets released on its own schedule, it gets its own (single, monotonically icreasing) version string. So I don't know how an automated algorithm can predict or sequence the version strings with *two* simultaneous version string in the same filename. > The tarball should arrive in its usual place at all the IF Archive > mirrors in a few days. It's all cleared of potential license snags. Thank you for your hard work with the license clarifications. > Correct md5 sum: > 85a34329badfecd8b586782890aa17bd inform-6.33-6.12.1.tar.gz Is there any chance to re-visit this naming scheme, and instead choose a single version scheme for this code base? Something conformant to <URL:http://semver.org/> would be appreciated, especially if the new release could have a version string that unambiguously sorts later than previous releases of the same code base. -- \ “[T]he question of whether machines can think … is about as | `\ relevant as the question of whether submarines can swim.” | _o__) —Edsger W. Dijkstra | Ben Finney <b...@benfinney.id.au>
signature.asc
Description: PGP signature
