Re: Anitya 0.14.0 (stg.release-monitoring.org) deployed on staging

Michal Konecny <mkonecny@xxxxxxxxxx> · Wed, 9 Jan 2019 11:01:35 +0100



    On 09/01/19 10:52, Igor Gnatenko wrote:

    
      Does it mean that packagers will start receiving
        the bugs again?
    
    Most of the issues with checking for new versions should be now
    fixed. But there is still issue with fedmsg messages being lost.
    This will be solved when fedmsg will be replaced by
    fedora-messaging.

    
        On Wed, Jan 9, 2019, 10:37 Michal Konecny <mkonecny@xxxxxxxxxx
          wrote:

        
        Hi
          everybody,

          
          I want to announce that the Anitya 0.14.0 was deployed on

          staging (https://stg.release-monitoring.org/)

          
          Feel free to test it.

          
          Anitya 0.14.0 will be deployed on production next week if no
          breaking

          issue will be found.

          
          You can see changelog here

          https://github.com/release-monitoring/anitya/releases/tag/0.14.0

          
          There are plenty of changes in this version. Here are most
          noticeable:

          * Delete cascade added to most db models - No orphaned
          packages or 

          mappings anymore \o/

          * Logs page is reworked - Should be much more simpler

          * Check is now done for all versions instead of only latest -
          No version 

          will be lost anymore

          * Rate limit is now handled more efficiently - No Github
          project should 

          be skipped anymore

          * New user management allowing simple promotion of users to
          admin - No 

          need to change configuration for every new admin

          * project.version.update fedmsg topic now contains information
          about 

          ecosystem - This should help when you are looking for projects
          from Pypi 

          or Rubygems

          * Support for Python 2.7 is now officially dropped

          
          Thanks to everyone who contributed to this new version.

          
          Regards,

          mkonecny

          _______________________________________________

          infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

          To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx

          Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html

          List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

          List Archives: 

          https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

          _______________________________________________

          infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

          To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx

          Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html

          List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines

          List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

        
      _______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx

    
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx