Please use tags for LÖVE versions

[martin-braun]

I consider building a CLI that allows someone to create a new LÖVE game by preparing a whole solution that contains everything you need from coding to deploying your game on and for each platform.

I even consider to add more script languages to it, like MoonScript or TypeScript. For the latter I want to automatically download your typings and put them into the project, however to let this work for each up-coming LÖVE version, it would be great if you could tag your typings in LÖVE versions.

That means, once typings for 11.1 are finished, you would make a tag called "11.1". For the latest LÖVE version I would simply grab the master until the tag is available, though.

Is this possible?

[hazzard993]

Sounds good!

I'll also note a change I intend to make to this repo's branching strategy that may be relevant for your program.

I'll make the master branch contain definitions for the latest LÖVE version. The head will be tagged with what version of LÖVE is being defined.

Previous LÖVE definitions will be placed in a support/<love version> branch. The heads of these will be tagged with <love version>.

master -- Contains LÖVE 2D definitions for the latest LÖVE version which the head is tagged with.
support/11.1 -- Contains the previous definitions for LÖVE 11.1. The head has the tag "11.1".

I'll work on tagging these now.

[martin-braun]

Thank you very much! And sure, you can also decide for branches instead of tagging. This way you keep your opportunity to fix older stuff, as long as things will be done, carefully, so it won't break my tool.

All in all this is future music, cuz everything needs to be done for Lua, first. I will keep you updated, though.