Need for release tar-ball about vehicle_signal_specification HOT 4 CLOSED

Did some investigation. There is no way to disable the automatic zip/tgz generation AFAIK, so we will get them anyway

• If we use a normal tarcommand, we will also get git-internal files.
• We could use something like git archive -o archive.tar.gz v4.1 but then we will not include submodules
• Alternatively we could do pip install git-archive-all and then for example git-archive-all --prefix=. out.tar.gz. Then we may get submodules if they have been checked out.

But do we want the submodules. VSS-tools might be handy, but Hugo used for documentation generation is maybe not that useful.

from vehicle_signal_specification.

Discussed at the meeting today, see https://wiki.covesa.global/display/WIK4/VSS+Meeting+Topics+and+Meeting+Notes

Summary: As this would require some extra work we should only do it if there is a good reason. Likely not needed if we keep the branches

from vehicle_signal_specification.

@g-scott-murray, see discussion above. As it would be some extra work, do you see a strong need for hand-made release tar ball if we save the release-branches for ever?

from vehicle_signal_specification.

MoM:

• Scott: Nice to have, but not essential if we keep release branches. if you have script it would be easy, otherwise fine to not include it
• Close for now

from vehicle_signal_specification.