New Upstream Release Monitoring Systems

[Petr Hracek]

On 02/20/2015 09:36 PM, Ralph Bean wrote:
> 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[1] 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
>    releases.
> - 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[2] 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[3].
> - Map the upstream project to a Fedora package in anitya[3].
> - Enable the monitoring flag for that Fedora package in pkgdb2[4].
>
> 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)[5] account
> while leaving the monitor flag set to False in pkgdb[4].
>
> If you encounter bugs or have requests for enhancement, as always please do
> file them[6][7][8].. and if you're having problems with a particular package
> there is a place to list those[8] also on the wiki page.
>
> [1] https://fedoraproject.org/wiki/Upstream_release_monitoring#Details
> [2] https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Packages_Monitored
> [3] https://release-monitoring.org
> [4] https://admin.fedoraproject.org/pkgdb
> [5] https://apps.fedoraproject.org/notifications
> [6] https://github.com/fedora-infra/anitya
> [7] https://github.com/fedora-infra/pkgdb2
> [8] https://github.com/fedora-infra/the-new-hotness
> [9] https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help
>
>
> _______________________________________________
> devel-announce mailing list
> devel-announce at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/devel-announce
>
>
Really nice and good work.

In our project called rebase-helper https://github.com/phracek/rebase-helper
we would like to analyze a new upstream version against an old upstream 
version
and let user now what is changed. E.g. Binaries are missing, soname bump 
change, header files are missing etc.

Is there any possibility how to integrate a tool (e.g. rebase-helper) to 
upstream release monitoring system?

Thanks for the good and hard work again.

-- 
Petr Hracek
Software Engineer
Developer Experience
Red Hat, Inc
Mob: +420777056169
email: phracek at redhat.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.fedoraproject.org/pipermail/devel/attachments/20150224/b2341de2/attachment.html>