> So Modularity will happily unleash experimental branches that were never intended to be released onto unsuspecting users of stable releases? How can this not be an absolute showstopper? This failed Modularity experiment needs to end NOW! As far as I know, there was no rule for the branch name, first and now. The modularity team did not create any limitation intentionally. There was a discussion to limit branch name in a past time. That's the why each developer can create the branch technically. Of course I know there is a document of a version branch name for modularity. In case of fNN branch of rpms/foo, it is created by below command like this. For example: https://bugzilla.redhat.com/show_bug.cgi?id=1326504#c35 ``` $ fedpkg request-branch --repo htslib f31 https://pagure.io/releng/fedora-scm-requests/issue/17764 ``` When running "fedpkg request-branch" command, the ticket is created newly. Then, someone can check the branch is valid or not, before it is actually created. So, that's no problem. The branch can not be created wrongly. But in case of module, each developer can create any branch technically under their responsibility, but they can not remove the branch, even it is created by mistake, and released in a short term. The rule "developer can not remove the branch they created and released" was created before the age of modurarity. I feel the rule can be adjusted considering current situation of modularity. -- Jun | He - His - Him _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
