You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would not put a download package in the documentation. In my opinion this is only used in OpenDRIVE, because it is not an open-source development. All our sources here are freely available.
So I would stick to links. You are right, we can put the release tag of the version in the link. But this can only be done very shortly before the actual release. Otherwise the links will be broken for a longer time. It is kind of a hen and egg problem. The links need to be correct in the release, but they can only be correct, after the release tag has been set.
But wouldn't it make the most sense to create a tag on the day of the TSC and create a release package 1.0 from it, which is then linked to from the documentation?
But wouldn't it make the most sense to create a tag on the day of the TSC and create a release package 1.0 from it, which is then linked to from the documentation?
Yes, but you need to create the links first, then create the tag. Otherwise the correct links are not part of the tagged commit.
Yes, of course, the links would be invalid until the release is published. I'd therefore integrate them into the documentation shortly before the release and then create the tag and the release package from that tag.
Is your feature request related to a problem? Please describe.
Right now we have the deliverable as links to the OpenMATERIAL 3D repository.
Describe the solution you'd like
I want to explore the following 2 options:
a) that we offer a downloadable package (similar to OpenDRIVE)
b) that we keep using links, but should point to a specific commit or tag (like the official release)
What do you think?
The text was updated successfully, but these errors were encountered: