Hello,

Two packages that I (co)maintain: python-stripe (3.4.0) and python-twilio
(7.12.0) have breaking changes in Fedora 37 compared to Fedora 36.

See migration notes:
https://github.com/stripe/stripe-python/wiki/Migration-Guide-for-v3 for
python-stripe
https://github.com/twilio/twilio-python/blob/main/CHANGES.md for
python-twilio

These packages are already in Fedora 37 repositories, but I hope that there
is still time to add this information to release notes of unreleased Fedora
37.

The reason for my mistake is that I have misread this phrase (
https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/#_rawhide):
> When a proposed update contains an ABI or API change: notify a week in
advance both the devel list and maintainers directly (using the
packagename-maintain...@fedoraproject.org alias) whose packages depend on
yours to rebuild or offer to do these rebuilds for them.

I thought that it is necessary to notify about the breaking changes only if
there are packages that depend on my package. Since there were no packages
depending on these packages, I have skipped the notification. Just recently
I understood that I should notify devel list in any case, since there
should be an update in release notes.

I am sorry for the trouble. I will not repeat my mistake again.

-- 
[image: Aiven] <https://www.aiven.io>
*Roman Inflianskas*
Software Engineer, *Aiven*
rom...@aiven.io   |  +358 503455168
aiven.io <https://www.aiven.io>   |    <https://www.facebook.com/aivencloud>
    <https://www.linkedin.com/company/aiven/>
<https://twitter.com/aiven_io>
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to