On Fri, 20 Feb 2015 22:34:27 -0600 James Cammarata <[email protected]> wrote:
> Hi Walter. > > No, we usually do not, since each distro packages the release at > their own speed and we don't keep track of them all. I know for EPEL, > it's usually about 2-3 weeks for the package to make its way out of > the testing branches, while for Ubuntu and others it is much sooner. As one of the Fedora/EPEL maintainers, FYI: I usually see new releases pretty quicky, do a quick test/scratch build and then go on to official builds. * Fedora Rawhide and pre-release Branched builds are done usually within hours of release, and appear in the next days rawhide/branched tree. * Fedora stable releases are also built in hours of release, but then are submitted as updates. They usually go out to updates-testing the next day. They have to spend 1 week in updates-testing or get +3 karma to go to updates. * EPEL releases are also built at the same time and submitted as updates. They usually go out to epel-testing the next day. They must spend 2 weeks in epel-testing or get +3 karma to go to updates. If you don't mind unsigned packages you can always get them direct from the buildsystem after they are built: https://koji.fedoraproject.org/koji/packageinfo?packageID=13842 You can test any of the testing updates and provide karma at: https://admin.fedoraproject.org/updates/search/ansible Hope that helps. kevin -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/20150221091338.15c74958%40voldemort.scrye.com. For more options, visit https://groups.google.com/d/optout.
pgpuCuFn1XGIT.pgp
Description: OpenPGP digital signature
