<html>
  <head>
    <meta content="text/html; charset=utf-8" http-equiv="Content-Type">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <div class="moz-cite-prefix">On 02/20/2015 09:36 PM, Ralph Bean
      wrote:<br>
    </div>
    <blockquote cite="mid:20150220203611.GA25350@geier" type="cite">
      <pre wrap="">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 <a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/pkgdb">https://admin.fedoraproject.org/pkgdb</a>
  It provides some flags used by the other systems.
- anitya is the web app running at <a class="moz-txt-link-freetext" href="https://release-monitoring.org">https://release-monitoring.org</a>
  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] <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Upstream_release_monitoring#Details">https://fedoraproject.org/wiki/Upstream_release_monitoring#Details</a>
[2] <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Packages_Monitored">https://fedoraproject.org/wiki/Upstream_release_monitoring#TLDR.3B_Get_Packages_Monitored</a>
[3] <a class="moz-txt-link-freetext" href="https://release-monitoring.org">https://release-monitoring.org</a>
[4] <a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/pkgdb">https://admin.fedoraproject.org/pkgdb</a>
[5] <a class="moz-txt-link-freetext" href="https://apps.fedoraproject.org/notifications">https://apps.fedoraproject.org/notifications</a>
[6] <a class="moz-txt-link-freetext" href="https://github.com/fedora-infra/anitya">https://github.com/fedora-infra/anitya</a>
[7] <a class="moz-txt-link-freetext" href="https://github.com/fedora-infra/pkgdb2">https://github.com/fedora-infra/pkgdb2</a>
[8] <a class="moz-txt-link-freetext" href="https://github.com/fedora-infra/the-new-hotness">https://github.com/fedora-infra/the-new-hotness</a>
[9] <a class="moz-txt-link-freetext" href="https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help">https://fedoraproject.org/wiki/Upstream_release_monitoring#Requesting_Help</a>
</pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
      <pre wrap="">_______________________________________________
devel-announce mailing list
<a class="moz-txt-link-abbreviated" href="mailto:devel-announce@lists.fedoraproject.org">devel-announce@lists.fedoraproject.org</a>
<a class="moz-txt-link-freetext" href="https://admin.fedoraproject.org/mailman/listinfo/devel-announce">https://admin.fedoraproject.org/mailman/listinfo/devel-announce</a></pre>
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <br>
    </blockquote>
    Really nice and good work.<br>
    <br>
    In our project called rebase-helper
    <a class="moz-txt-link-freetext" href="https://github.com/phracek/rebase-helper">https://github.com/phracek/rebase-helper</a><br>
    we would like to analyze a new upstream version against an old
    upstream version<br>
    and let user now what is changed. E.g. Binaries are missing, soname
    bump change, header files are missing etc.<br>
    <br>
    Is there any possibility how to integrate a tool (e.g.
    rebase-helper) to upstream release monitoring system?<br>
    <br>
    Thanks for the good and hard work again.<br>
    <br>
    <pre class="moz-signature" cols="72">-- 
Petr Hracek
Software Engineer
Developer Experience
Red Hat, Inc
Mob: +420777056169
email: <a class="moz-txt-link-abbreviated" href="mailto:phracek@redhat.com">phracek@redhat.com</a></pre>
  </body>
</html>