-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75... ea749cb - -- - -Igor Gnatenko
On Tue, Jan 23, 2018 at 2:48 PM, Igor Gnatenko ignatenkobrain@fedoraproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75... ea749cb
This was announced to all package owners depending on tinyxml2 right after the build succeed on f28 (unless I missed any). Most rebuilds are already done.
- -Igor Gnatenko
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpnPSEACgkQaVcUvRu8 X0zgYBAAqfV6lP/OHdB/tsCsojIw/xjjSt+1jhQzuBO6Hlk22vUDkXeeueJG2IQF ej/eXR8/+GYOrV73vfH4z8XTWzbQuPWhnXak8qnJ052riwkr1lI1kLsD+IKi82kt cQDNGJ6BwMydIzUVYpF9XzCVMh8NdKtrS2VIBz4NjJk9jLhqVPY1kfm0qakTdpSI YajRfp4dlSwMC/LvUriY5I3aOIpogKKBog+VDxEUBhE9MI31af5ZX81RYJRA+lrT RXYxZHUc5b4xJ1vaUAziOYOZVfq2pE/rr+8aKtL4m+StKc09aHyYdF8p1zZAycpK mKdKs9mkR16E+Kjn3JriMtMH/BpenZ9yntKIH9wxOKmdFfD4UfoyBrx8/ZE09NkO ir23M8jOqteTxqtprnuNKBjjOZxUXbErYgvnaOFCdFYkkJZQtsk0dypGWYXI6QRh UYwxEvvWCXaFfBbOFoMXWUrkqqVEO+l6wWmXkW57HGpFMbsgiOddDzflUKMdif3+ qA0ObL72ndekshPdZcaaD12OBNVYkgffgsHcd6VDA9h815iKS720X/uKRt5eBP9n 7XyJtOV/JSMwvh+CVnDqY+oqKW+FbCV8l1VeE7E2nSTHwSG8z5IG6cIrjfdYtaAK OvTuRC0vimeDS7c9fpp2TFEmZ63pN4Tsfq+hF1Ch0gR5etJZQuA= =1M6s -----END PGP SIGNATURE-----
François Cami wrote:
On Tue, Jan 23, 2018 at 2:48 PM, Igor Gnatenko ignatenkobrain@fedoraproject.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75...
ea749cb
This was announced to all package owners depending on tinyxml2
announcement should be made here too
-- rex
announcement should be made here too
Okay, so I'm officially confused.
https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master says: "For updates to rawhide packages, Maintainers SHOULD: (...) A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them "
so while I should have notified the affected packages' maintainers a week in advance, I would have notified fedora-devel if that was stated there.
Should we update the update policy?
On Tue, Jan 23, 2018 at 09:01:56PM -0000, François Cami wrote:
Okay, so I'm officially confused. https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master says: "For updates to rawhide packages, Maintainers SHOULD: (...) A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them "
so while I should have notified the affected packages' maintainers a week in advance, I would have notified fedora-devel if that was stated there.
Should we update the update policy?
Rule of thumb: more communication is better.
announcement should be made here too
+
Rule of thumb: more communication is better.
Ack.
Change proposal for https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
"A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them." => "A week in advance, notify fedora-devel so that maintainers whose packages depend on yours can rebuild when there are abi/api changes or offer to do these rebuilds for them."
As this seems to be the consensus I'll push the change before the end of the week. Comments welcome!
On Wed, Jan 24, 2018 at 08:21:30AM -0000, François Cami wrote:
announcement should be made here too
Rule of thumb: more communication is better.
Ack.
Change proposal for https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
"A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them." => "A week in advance, notify fedora-devel so that maintainers whose packages depend on yours can rebuild when there are abi/api changes or offer to do these rebuilds for them."
As this seems to be the consensus I'll push the change before the end of the week. Comments welcome!
The list and the maintainers is likely the ideal case :)
Pierre
On Wed, 2018-01-24 at 09:34 +0100, Pierre-Yves Chibon wrote:
On Wed, Jan 24, 2018 at 08:21:30AM -0000, François Cami wrote:
announcement should be made here too
Rule of thumb: more communication is better.
Ack.
Change proposal for https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
"A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them." => "A week in advance, notify fedora-devel so that maintainers whose packages depend on yours can rebuild when there are abi/api changes or offer to do these rebuilds for them."
As this seems to be the consensus I'll push the change before the end of the week. Comments welcome!
The list and the maintainers is likely the ideal case :)
+1 - I'd say a mail to the list *and* directly to each affected maintainer. devel@ is a firehose and some maintainers may not keep up with it.
On Wed, 24 Jan 2018 09:57:03 +0100 Adam Williamson adamwill@fedoraproject.org wrote:
On Wed, 2018-01-24 at 09:34 +0100, Pierre-Yves Chibon wrote:
On Wed, Jan 24, 2018 at 08:21:30AM -0000, François Cami wrote:
announcement should be made here too
Rule of thumb: more communication is better.
Ack.
Change proposal for https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
"A week in advance, notify maintainers who depend on their package to rebuild when there are abi/api changes that require rebuilds in other packages or offer to do these rebuilds for them." => "A week in advance, notify fedora-devel so that maintainers whose packages depend on yours can rebuild when there are abi/api changes or offer to do these rebuilds for them."
As this seems to be the consensus I'll push the change before the end of the week. Comments welcome!
The list and the maintainers is likely the ideal case :)
+1 - I'd say a mail to the list *and* directly to each affected maintainer. devel@ is a firehose and some maintainers may not keep up with it.
isn't devel-announce better fit than devel? Because its description [1] lists "- ABI changes or rawhide package changes that require maintainer coordination. "
[1] https://lists.fedoraproject.org/admin/lists/devel-announce.lists.fedoraproje...
Dan
On Wed, Jan 24, 2018 at 10:05:56AM +0100, Dan Horák wrote:
+1 - I'd say a mail to the list *and* directly to each affected maintainer. devel@ is a firehose and some maintainers may not keep up with it.
isn't devel-announce better fit than devel? Because its description [1] lists "- ABI changes or rawhide package changes that require maintainer coordination. "
I think that's probably a judgment call based on how many people will be affected. If we put too much on devel-announce, it'll have the same firehose-of-information problem as devel.
On Wed, Jan 24, 2018 at 11:15 AM, Matthew Miller mattdm@fedoraproject.org wrote:
On Wed, Jan 24, 2018 at 10:05:56AM +0100, Dan Horák wrote:
+1 - I'd say a mail to the list *and* directly to each affected maintainer. devel@ is a firehose and some maintainers may not keep up with it.
isn't devel-announce better fit than devel? Because its description [1] lists "- ABI changes or rawhide package changes that require maintainer coordination. "
I think that's probably a judgment call based on how many people will be affected. If we put too much on devel-announce, it'll have the same firehose-of-information problem as devel.
Isn't it also moderated? Which would mean the moderator has to be paying attention and let it through...
I like devel +maintainers directly.
josh
On Wed, Jan 24, 2018 at 11:15 AM, Matthew Miller <mattdm(a)fedoraproject.org> wrote:
Isn't it also moderated? Which would mean the moderator has to be paying attention and let it through...
I like devel +maintainers directly.
We seem to have reached consensus in that either devel or devel-announce should be used so I've updated https://fedoraproject.org/w/index.php?title=Updates_Policy to be better aligned with this (using devel for now).
-- François
-
Adam Williamson -
Dan Horák -
François Cami -
François Cami -
Igor Gnatenko -
Josh Boyer -
Matthew Miller -
Pierre-Yves Chibon -
Rex Dieter