Hello,
is there a general recommendation regarding keeping git release branches
separate vs merged? I have been keeping mine separate. Originally to
avoid release and changelog conflicts when cherry-picking, but I got
used to it and kept doing it after converting to %autorelase and
%autochangelog.
Recently one of my packages got it branches merged by a provenpackager
doing a deps rebuild. If there is no policy to merge, this is
disappointing as force-pushes as not allowed and branches once merged
cannot be unmerged. I know this is just a cosmetic issue, but choices
made by the primary maintainers should be respected IMO.
Best regards,
Julian
--
_______________________________________________
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
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
