Modularity team, On below definition of the modularity document, there is a problem, as Vit said. https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-guidelines/#_package_branch_name The problem is If we use X.Y.Z as a package branch name with rpms/bar, for example the situation is like this. modules/foo 2.5 rpms/foo 2.5 rpms/bar 2.5 In this case, seeing rpms/bar 2.5 branch, people tend to recognize it, "bar"'s 2.5 branch. But it's wrong. It can be actually bar 1.2.3 that is included in module foo 2.5. rpms/bar's situation means "rpms/<another> package branch" in the list. You see several patterns in it. Maybe I covered most modules situation. https://pagure.io/jaruga-modules-branches postgresql module solves the situation like this. modules/foo 11 rpms/foo stream-postgresql-11 rpms/bar stream-postgresql-11 reviewboard module solves the situation like this. modules/foo 3.0 rpms/foo 3.0 rpms/bar 1.2 (it means bar 1.2 version's branch) I wish at least recommended way is documented in the modularity section of the page. -- Jun _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
