ign ➡️ gz

[chapulina]

• Part of Rename Ignition to Gazebo release-tools#698

• Builds on top of [ign ➡️ gz] URLs #111

• For versions < Garden: update only repository URLs

• For Garden

  • URLs
  • Update directory names
  • Move ign-*.yaml to gz-*.yaml

[chapulina]

I started trying to fix Windows CI using this branch on gazebo-tooling/release-tools@master...chapulina/gazebodistro_gz, but I'm starting to wonder if we shouldn't just move all files and change all directory names (even not Garden).

Maintaining a single format will be easier in the long run. The downside is potentially breaking users of versions < Garden that rely on gazebodistro - but we've never promised this would be stable, so I think it may be worth the change.

Any thoughts, @j-rivero ?

[methylDragon]

LGTM! We'll need to remember to gz-gazebo7.yaml -> gz-sim7.yaml once we migrate the project names though

[j-rivero]

but I'm starting to wonder if we shouldn't just move all files and change all directory names (even not Garden).

Maintaining a single format will be easier in the long run. The downside is potentially breaking users of versions < Garden that rely on gazebodistro - but we've never promised this would be stable, so I think it may be worth the change.

I found the same blocker while testing gazebo-tooling/release-tools#738 and #112. It would be great if we use the same names for all the files and at the same time maintain the current file names, something that we could probably accomplish on UNIX using symlinks. On Windows I would prefer to skip the symlink management so the option could be to duplicate the old files (previous to Garden) to have ign- and gz- with the obvious cost of maintenance and introducing a possible source of problems. I'm only proposing this since these files rarely change but I can be convinced otherwise.

[j-rivero]

Let's follow in #117