# Ansible 2.5.0 Release Candidate 3 is available

**URL:** <https://forum.ansible.com/t/ansible-2-5-0-release-candidate-3-is-available/27009>\
**Category:** Ansible Developer\
**Created:** [March 16, 2018, 1:31am UTC](https://forum.ansible.com/t/ansible-2-5-0-release-candidate-3-is-available/27009 "2018-03-16T01:31:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/ansible/original/1X/1882d9a01da5d8996a862359b0913cc568a39b84.svg) [@system](https://forum.ansible.com/u/system)\
**Post date:** [March 16, 2018, 1:31am UTC](https://forum.ansible.com/t/ansible-2-5-0-release-candidate-3-is-available/27009/1 "2018-03-16T01:31:30Z")

</div>

Hi all- we’re happy to announce that Release Candidate 3 of Ansible 2.5.0 is now available!

How do you get it?

---

<div class="post-metadata">

**Author:** ![Andreas\_Olsson](https://avatars.discourse-cdn.com/v4/letter/a/ba9def/32.png) [@Andreas\_Olsson](https://forum.ansible.com/u/Andreas_Olsson)\
**Post date:** [March 18, 2018, 5:08am UTC](https://forum.ansible.com/t/ansible-2-5-0-release-candidate-3-is-available/27009/2 "2018-03-18T05:08:22Z")

</div>

tor 2018-03-15 klockan 18:31 -0700 skrev mattdavi@redhat.com:

> The tar.gz of the release can be found here:
> 
> [http://releases.ansible.com/ansible/ansible-2.5.0rc3.tar.gz](http://releases.ansible.com/ansible/ansible-2.5.0rc3.tar.gz)  
> SHA256: 0fde8eb02a34ba1936a52da423d339ac9bded6aeac8d13d90f1f0be812c5b877  
> ...

Instead of linking to [http://releases.ansible.com/](http://releases.ansible.com/), wouldn't it be  
better to link to [https://releases.ansible.com/](https://releases.ansible.com/)? That is, using  
https:// rather than http://.

// Andreas

---

<div class="post-metadata">

**Author:** ![Rene\_Moser](https://avatars.discourse-cdn.com/v4/letter/r/7bcc69/32.png) [@Rene\_Moser](https://forum.ansible.com/u/Rene_Moser)\
**Post date:** [March 18, 2018, 12:25pm UTC](https://forum.ansible.com/t/ansible-2-5-0-release-candidate-3-is-available/27009/3 "2018-03-18T12:25:42Z")

</div>

Hi Matt and Ansible realease team

The letsencrypt maintaniers would like to request consideration of [https://github.com/ansible/ansible/pull/37572](https://github.com/ansible/ansible/pull/37572) to be in 2.5 final.

This rather small patch, fixes an issue with the wildcard certificate support, which was released by Letsencrypt just a few couple of days ago. The implementation for wildcard certificate support in the letsencrypt module for 2.5 was only possible with an enormous effort by Felix Fontein (felixfontein), who worked closely with Letsencrypt, I see the value for Ansible to have an excellent support for the latest feature of letsecrypt is considerable and that is why I vote for this patch to be included in 2.5 final.

Thanks

René (resmo)