ABRT server to start publishing to Fedmsg
by Marek Brysa
Hi everyone,
We're excited to announce that the ABRT server [1] will start publishing to Fedmsg. Currently there are two general topics available:
* faf.report.threshold{1,10,100,1000,10000,100000,1000000} is fired whenever a crash report occurrence reaches the given threshold.
* faf.problem.threshold{1,10,100,1000,10000,100000,1000000} is the same, but for problems (similar crash reports clustered together)
Both contain names of the affected package, so you can easily configure email notifications about packages you maintain on the FMN [2], e.g. you could be notified whenever a crash occurs in your package 1 000 times and start investigating the problem. By default, packagers will receive all notifications with a threshold of 10 and higher for their packages, but you may want to prune those down to only problems with more frequent occurrence.
Please feel free to contact us [3,4] with any questions, suggestions, issues or feature request.
For the ABRT and Fedmsg teams,
Marek
[1] https://retrace.fedoraproject.org/faf/
[2] https://apps.fedoraproject.org/notifications/
[3] https://github.com/abrt/faf or #abrt on freenode
[4] http://www.fedmsg.com/en/latest/#community
8 years, 11 months
F23 System Wide Change: Mono 4
by Jan Kurik
= Proposed System Wide Change: Mono 4 =
https://fedoraproject.org/wiki/Changes/Mono_4
Change owner(s): Claudio Rodrigo Pereyra Diaz <elsupergomez(a)fedoraproject.org>
Update the Mono stack in Fedora from 2.10 to 4.*
== Detailed Description ==
Support for Mono versions 3.0 and 2.10 is been discontinued. No further development of bug fixing is planned for those branches. Mono 4 is the active branch an have many improvements . See upstream notes http://www.mono-project.com/docs/about-mono/releases/4.0.0/
Mono require it self to build. Actual version 2.10.8 is to old to build version 4 that require at less version 3.4. At the moment on copr we use monolite a little version of mono compiler shipped in the tarball for first build time.
We have two option to upgrade:
* Upgrade mono to version 3.4, then to version 3.12 and then to version 4.0.1 on rawhide (actually 3.4 don't build on rawhide this need fixed)
* Make a one time exception of the rule for build mono 4.0.1-1 using monolite, later make mono depend again on it self and rebuild mono 4.0.1-2 using mono-4.0.1-1 .
== Scope ==
* Proposal owners: Update mono spec and build in copr and/or koji until is ready.
* Other developers: See Upgrade/compatibility impact and Dependencies section
* Release engineering: None
* Policies and guidelines: None
--
Jan Kuřík
8 years, 11 months
