Hi,
Just for your information, ]project-open[ has switched to GIT some years ago. We are running a GitLab instance with a separate repo for every package, because we need to keep some packages private (>100 "customer packages" plus some closed-source packages). Normally we track versions only per package.
However, one of our customers has asked us to maintain release information with versions for all packages.
So we have created a new "packages" repo that contains the ~200 ]po[ packages as GIT "submodules". We've also created a GUI that lists "releases" (commits on the "packages" repo) together with the included commits on the individual packages. That's nothing big, but it's nice to be able to show the users their current release with the specific changes, also linked to the customer's internal bug-tracker with manages the development pipeline. Contact me if you want the code. Also, we've created a GIT pre-commit hook that automatically increases the package version number (per package).
I've heard mixed reports about using GIT submodules in the past, but the negative reports seem to be due to confusion (mental model not matching reality 😊.
Cheers!
Frank
