Releases versus folders

[ejhumphrey]

It seems the tradition here has been to copy-create a new folder for each year. This is in contrast to a more typical git workflow where there would only ever be one template, and different releases are tagged for different conferences.

This could be good to get in front of for ISMIR2019. What are your thoughts @f0k + @stefan-balke, as contributors? or @julian-urbano on behalf of the program co-chairs?

[julian-urbano]

It does indeed make more sense to just commit new changes. Last I heard, @stefan-balke was going to update the template for 2019?

On a related topic, it's very likely that new templates will be made at least for the LBD papers, so some explicit folder-like division will be necessary for paper types.

[stefan-balke]

I'm fine with anything. However, a conference would be a release but what about TISMIR? Putting it into a separate repo?

@julian-urbano since the merge is done now, I'll make a PR ASAP.

[stefan-balke]

And yes, let's keep this in mind but I would like to leave it as is for this year...

[f0k]

However, a conference would be a release but what about TISMIR? Putting it into a separate repo?

Sorry I'm late to the party, but yes, switching to releases would require separate repositories for the conference (which could still have subfolders for paper and LBD and MIREX templates released together) and TISMIR. Which wouldn't be a bad idea anyway, since they're not sharing anything now.