[Fwd: New Upstream Release Monitoring Systems]
sanjay.ankur at gmail.com
Fri Feb 20 21:37:39 UTC 2015
A post on this would be awesome. I'll try and write one tomorrow.
-------- Forwarded Message --------
> From: Ralph Bean
> Subject: New Upstream Release Monitoring Systems
> Date: Fri, 20 Feb 2015 15:36:11 -0500
> I'm proud to announce that the Infrastructure team has finished deploying the
> first iteration of our replacement for the older, wiki-based Upstream Release
> Monitoring tools this week. You can read about the details of the trio of
> systems now used to coordinate upstream release monitoring on the same old
> wiki page.
> Names of systems:
> - pkgdb is the familiar Fedora Package DB https://admin.fedoraproject.org/pkgdb
> It provides some flags used by the other systems.
> - anitya is the web app running at https://release-monitoring.org
> It is responsible for scraping upstream release sites looking for new
> - the-new-hotness is a backend daemon that responds to fedmsg messages about
> upstream releases.
> The bugs filed in bugzilla look much the same as they did before, but for
> packagers there is one thing to note: the process of getting your package(s)
> registered for upstream release monitoring has changed. Please see the
> instructions on the wiki page.
> Old packages that were listed on the wiki page have been imported to
> release-monitoring.org and have had their monitoring flag set in pkgdb. New
> packages added to Fedora now have their monitoring flag set to True by default
> and a script attempts to map them to an upstream project in
> release-monitoring.org automatically.
> If you want new upstream releases monitored for your package(s), you must:
> - Add the upstream project to anitya.
> - Map the upstream project to a Fedora package in anitya.
> - Enable the monitoring flag for that Fedora package in pkgdb2.
> Note also that it is now possible to get notifications about upstream releases
> without bugs being filed in bugzilla. To do this, add your projects to
> release-monitoring.org and configure your Fedora Notifications (FMN) account
> while leaving the monitor flag set to False in pkgdb.
> If you encounter bugs or have requests for enhancement, as always please do
> file them.. and if you're having problems with a particular package
> there is a place to list those also on the wiki page.
>  https://fedoraproject.org/wiki/Upstream_release_monitoring#Details
>  https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Packages_Monitored
>  https://release-monitoring.org
>  https://admin.fedoraproject.org/pkgdb
>  https://apps.fedoraproject.org/notifications
>  https://github.com/fedora-infra/anitya
>  https://github.com/fedora-infra/pkgdb2
>  https://github.com/fedora-infra/the-new-hotness
>  https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 473 bytes
Desc: This is a digitally signed message part
More information about the marketing