Re: New Upstream Release Monitoring Systems

2015-04-21 Thread Petr Hracek
On 02/24/2015 05:58 PM, Ralph Bean wrote: On Tue, Feb 24, 2015 at 12:33:29PM +0100, Petr Hracek wrote: 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.

Re: New Upstream Release Monitoring Systems

2015-04-14 Thread Petr Hracek
On 02/24/2015 05:58 PM, Ralph Bean wrote: On Tue, Feb 24, 2015 at 12:33:29PM +0100, Petr Hracek wrote: 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.

Re: New Upstream Release Monitoring Systems

2015-03-01 Thread Michael Schwendt
On Fri, 20 Feb 2015 15:36:11 -0500, Ralph Bean wrote: If you encounter bugs or have requests for enhancement, as always please do file them[6][7][8].. Done. Thanks for a premature April Fool's prank. ;) -- devel mailing list devel@lists.fedoraproject.org

Re: New Upstream Release Monitoring Systems

2015-02-25 Thread Pierre-Yves Chibon
On Tue, Feb 24, 2015 at 11:42:49AM -0700, Dave Johansen wrote: On Tue, Feb 24, 2015 at 9:51 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Tue, Feb 24, 2015 at 10:33:34AM -0600, Michael Catanzaro wrote: A A This looks cool. A A On Fri, Feb 20, 2015 at 2:36 PM,

Re: New Upstream Release Monitoring Systems

2015-02-25 Thread Pierre-Yves Chibon
On Wed, Feb 25, 2015 at 03:08:40PM +0100, Vít Ondruch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dne 24.2.2015 v 14:25 Pierre-Yves Chibon napsal(a): https://release-monitoring.org/projects/updates/failed Weird pagination When you filter? Yes I found this out and it's

Re: New Upstream Release Monitoring Systems

2015-02-25 Thread Vít Ondruch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dne 24.2.2015 v 14:25 Pierre-Yves Chibon napsal(a): https://release-monitoring.org/projects/updates/failed Weird pagination Vít -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJU7ddnAAoJEAzgnueZF7h8BGYP/jCRcMcGX2jDnd0tegwer9I8

Re: New Upstream Release Monitoring Systems

2015-02-25 Thread Vít Ondruch
Dne 25.2.2015 v 15:23 Pierre-Yves Chibon napsal(a): On Wed, Feb 25, 2015 at 03:08:40PM +0100, Vít Ondruch wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dne 24.2.2015 v 14:25 Pierre-Yves Chibon napsal(a): https://release-monitoring.org/projects/updates/failed Weird pagination

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Matthias Runge
On Fri, Feb 20, 2015 at 03:36:11PM -0500, 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

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread 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

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Pierre-Yves Chibon
On Tue, Feb 24, 2015 at 12:33:29PM +0100, Petr Hracek wrote: On 02/20/2015 09:36 PM, Ralph Bean wrote: 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

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Pierre-Yves Chibon
On Tue, Feb 24, 2015 at 09:59:24AM +1000, Dan Callaghan wrote: Excerpts from Ralph Bean's message of 2015-02-21 06:36 +10:00: 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

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Michael Catanzaro
This looks cool. On Fri, Feb 20, 2015 at 2:36 PM, Ralph Bean rb...@redhat.com wrote: - Enable the monitoring flag for that Fedora package in pkgdb2[4]. I think this is the step people will forget to do. If there was at least a reminder on the release-monitoring website, that would be

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Pierre-Yves Chibon
On Tue, Feb 24, 2015 at 10:33:34AM -0600, Michael Catanzaro wrote: This looks cool. On Fri, Feb 20, 2015 at 2:36 PM, Ralph Bean rb...@redhat.com wrote: - Enable the monitoring flag for that Fedora package in pkgdb2[4]. I think this is the step people will forget to do. If

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Dave Johansen
On Tue, Feb 24, 2015 at 9:51 AM, Pierre-Yves Chibon pin...@pingoured.fr wrote: On Tue, Feb 24, 2015 at 10:33:34AM -0600, Michael Catanzaro wrote: This looks cool. On Fri, Feb 20, 2015 at 2:36 PM, Ralph Bean rb...@redhat.com wrote: - Enable the monitoring flag for that Fedora

Re: New Upstream Release Monitoring Systems

2015-02-24 Thread Ralph Bean
On Tue, Feb 24, 2015 at 12:33:29PM +0100, Petr Hracek wrote: 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

Re: New Upstream Release Monitoring Systems

2015-02-23 Thread Dan Callaghan
Excerpts from Ralph Bean's message of 2015-02-21 06:36 +10:00: 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

New Upstream Release Monitoring Systems

2015-02-20 Thread Ralph Bean
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

New Upstream Release Monitoring Systems

2015-02-20 Thread Ralph Bean
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