f6aa83acfe
The UI bundle now includes a toc in the right hand sidebar, so there's no need to have tocs explicitly at the start of documents.
94 lines
4.7 KiB
Text
94 lines
4.7 KiB
Text
= Upstream Release Monitoring
|
|
|
|
[#tldr_get_packages_monitored]
|
|
== TLDR; Get Packages Monitored
|
|
|
|
Get bug reports for a project's releases in Fedora's Bugzilla with three steps:
|
|
|
|
. Add the project to https://release-monitoring.org[Anitya].
|
|
. Map the project to a Fedora package in Anitya.
|
|
. Tweak the monitoring setting for your packages at https://src.fedoraproject.org[Fedora Package Sources].
|
|
|
|
[#bugzilla_bugs_by_the_new_hotness]
|
|
== Bugzilla bugs by the-new-hotness
|
|
|
|
* https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&bug_status=POST&classification=Fedora&columnlist=product%2Ccomponent%2Cassigned_to%2Cbug_status%2Cresolution%2Cshort_desc%2Cchangeddate%2Copendate&email1=upstream-release-monitoring%40fedoraproject.org&emailreporter1=1&emailtype1=substring&list_id=1733771&order=changeddate%20DESC%2Cbug_id%20DESC&query_based_on=&query_format=advanced[OPEN bugs]
|
|
|
|
* https://bugzilla.redhat.com/buglist.cgi?bug_status=CLOSED&classification=Fedora&email1=upstream-release-monitoring%40fedoraproject.org&emailreporter1=1&emailtype1=substring&order=changeddate%20DESC%2Cbug_id%20DESC&query_based_on=&query_format=advanced[CLOSED bugs]
|
|
|
|
== Details
|
|
|
|
One of the core foundation of Fedora is _First_
|
|
which implies having the latest versions of software
|
|
(in rawhide and sometimes in released branches),
|
|
but as a package maintainer
|
|
it can be tedious to keep up with the releases from multiple projects.
|
|
|
|
Fedora thus offers a service to help with this.
|
|
This service is divided into three components:
|
|
|
|
* Anitya
|
|
* monitoring settings at Fedora Package Sources
|
|
* https://github.com/fedora-infra/the-new-hotness/[The-new-hotness]
|
|
|
|
=== Anitya
|
|
|
|
Available at https://release-monitoring.org[release-monitoring.org],
|
|
Anitya provides a web service where anyone can register a project.
|
|
Anitya will then broadcast a http://fedmsg.com[fedmsg] message
|
|
when it finds a new release.
|
|
Checks are run by cron twice a day.
|
|
|
|
Anitya is not specific to Fedora
|
|
but we are using it as a way to learn about new releases.
|
|
Edit entries there to your heart's content.
|
|
|
|
Bugs, features request and patches should go to https://github.com/fedora-infra/anitya/issues[anitya/issues].
|
|
|
|
[#monitoring_settings_at_src.fedoraproject.org]
|
|
=== Monitoring settings at src.fedoraproject.org
|
|
|
|
Fedora package maintainers can use the bottom left column
|
|
at the package's page at https://src.fedoraproject.org/[src.fedoraproject.org]
|
|
to have it monitored by the-new-hotness (see below).
|
|
|
|
[#the_new_hotness]
|
|
=== The-New-Hotness
|
|
|
|
https://github.com/fedora-infra/the-new-hotness/[The-new-hotness] is an application that listens to the fedmsg bus
|
|
and acts upon receiving messages from https://release-monitoring.org[release-monitoring.org].
|
|
|
|
When it receives a message indicating that a project has a new release,
|
|
and that project is mapped to a Fedora package,
|
|
it will check in pkgdb2 if the Fedora package is marked to be monitored.
|
|
|
|
If the package is marked to be monitored,
|
|
the-new-hotness will open a ticket on https://bugzilla.redhat.com[Bugzilla]
|
|
mentioning the availability of the new release.
|
|
It will then clone the git repository,
|
|
bump the version and reset the release,
|
|
download the new sources (if it can)
|
|
and attempt a scratch build in koji.
|
|
|
|
The result of the scratch build is then added to the open bugzilla ticket.
|
|
|
|
Subsequent successful koji builds are added to the ticket as well.
|
|
|
|
NOTE: In some cases the scratch build will always fail
|
|
(for example if the `Source0` in the spec file cannot be adjusted automatically),
|
|
if you wish to avoid receiving the notification that the scratch-build failed,
|
|
you can set the monitoring flag in pkgdb2 to _nobuild_ (or _Bugs only_).
|
|
Then the bugzilla ticket will be created upon finding a new version,
|
|
but no scratch build will be made.
|
|
|
|
[#related_projects]
|
|
== Related Projects
|
|
|
|
* http://github.com/tannewt/open-source-watershed[OSWatershed] - Monitors several distributions at once
|
|
* https://ppisar.fedorapeople.org/cpandistributionsinfedora.xhtml[Perl package monitoring]
|
|
* http://rpms.famillecollet.com/rpmphp/[Reports from Remi] PECL, pear and R extensions upstream comparison and stable repo with rawhide comparison for all packages
|
|
* http://distrowatch.com/table.php?distribution=fedora[DistroWatch.com: Fedora]
|
|
* http://youri.zarb.org/[Youri] http://check.mageia.org/[in action] http://svnweb.mageia.org/adm/puppet/modules/youri-check/[puppet modules] A generic framework
|
|
* https://github.com/jness/ossvt[ossvt] Developed for https://ius.io/[IUS]
|
|
* https://fedorapeople.org/cgit/till/public_git/cnucnu.git/[cnucnu] — the tool previously used to provide this service for Fedora
|
|
* http://repology.org/metapackages/outdated-in-repo/fedora_rawhide/[Repology] cross distro version comparision
|