Updates policy exception for go2rpm #3610
Labels
No labels
document it
fast track
meeting
next release
nonresponsive maintainer
packager revocation
pending announcement
provenpackager
python 2 exception
self contained change
stalled
Status
Accepted
Status
Duplicate
Status
Insufficient data
Status
Invalid
Status
Rejected
system wide change
updates policy exception
vote-in-progress
No milestone
No project
No assignees
8 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
fesco/tickets#3610
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hi, I'd like to request an Updates Policy exception for go2rpm, the specfile generator used by packagers in the Go ecosystem, as I expect to make some changes that technically could be considered breaking upstream and release them across stable branches. Note that this request only concerns the go2rpm CLI interface that packagers can optionally use to generate specfiles. This is not about the Go RPM macros which are part of a separate package. It's important to Go packagers that the same version of go2rpm is available across all Fedora releases with consistent behavior so I'd like to be able to keep versions in sync.
+1
Metadata Update from @decathorpe:
+1
Given that you are upstream, could you commit to making an announcement on fedora-devel list ahead of landing any such breaking changes in the stable repos, similarly to how someone would pre-announce a soname bump in Rawhide? It will help reduce surprises.
+1
+1
+1
+1
+1
After 7 days:
APPROVED(+7, 0, 0)
Metadata Update from @siosm:
Metadata Update from @fale:
Announced https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/KDZUYE4YHI5PQVKNBVLUVISRRSAZ4553/
fesco/docs#141
PR merged. Thanks!
Metadata Update from @decathorpe: