l behaves, as opposed
> to "pip install ansible", after the release happens.
>
> Alan
> github: AlanCoding
>
>
> On Fri, May 1, 2020 at 1:01 PM Toshio Kuratomi
> wrote:
>
>> Where are you getting ansible-base from? The best solution might be to
>> put
e:
https://github.com/ansible-collections/
* Bugs in the way the new ansible is packaged:
https://github.com/ansible-community/antsibull
If you aren't sure where to file the bug, pick which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
You re
m/ansible-community/antsibull
If you aren't sure where to file the bug, pick which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development&
elevant collection repo, normally one of the repos here:
https://github.com/ansible-collections/
* Bugs in the way the new ansible is packaged:
https://github.com/ansible-community/antsibull
If you aren't sure where to file the bug, pick which you feel is
closest and the Community Team wil
ere:
https://github.com/ansible-collections/
* Bugs in the way the new ansible is packaged:
https://github.com/ansible-community/antsibull
If you aren't sure where to file the bug, pick which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
Hi all, Ansible-2.10 has been a big change in how we develop Ansible
with development split between the ansible-base and ansible packages.
Although the development schedule has been known for a long time,
we're only finalizing the release schedule for Ansible-2.10.0 now.
Here is the release schedu
he way the new ansible is packaged:
https://github.com/ansible-community/antsibull
If you aren't sure where to file the bug, pick which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscr
I don't have answers to your question but I wonder about your use
case. Directories are seldom left empty so it seems like this is more
about taking action to empty a directory than it does to assert that
the state of the system includes the emptied directory. That can be
an important distinction
nity/antsibull
If you aren't sure where to file the bug, pick which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscr
draft document which includes where to report bugs on various parts
of the ansible package:
https://github.com/ansible/community/wiki/User-testing-of-ansible-2.10-pre-releases
If you aren't sure where your bug falls, pick which you feel is
closest and the Community Team will always move it if
Greetings all, in preparation for the beta1 release on the first of
September, the ansible package is now feature frozen.
What does that mean exactly?
The main goal of the 2.10.x package is to give end users a smooth
transition from the monolitihic approach to content in ansible-2.9 to
the ecosys
Greetings collection maintainers!
I have an important update to the Ansible-2.10.0 release schedule that
affects you.
== Summary: The important bits ==
I announced feature freeze for Ansible 2.10.0 last week. However,
after a group of collections told me that they have a coordinated new
feature
k which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send a
://raw.githubusercontent.com/ansible/community/master/meetings/ical/community.ics
* 22-Sep-2020: If no blockers are found, ansible-2.10.0 final will
release as previously scheduled.
Thanks for understanding!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google
ser-testing-of-ansible-2.10-pre-releases
If you aren't sure where your bug falls, pick which you feel is
closest and the Community Team will always move it if needed
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Devel
n towards fixing anything that wasn't noticed previously in the
Ansible-2.10.1 release. So please test out the beta and release
candidate now and report candidate blockers before the meeting.
Thank you,
Toshio Kuratomi
On Tue, Sep 1, 2020 at 11:21 PM Toshio Kuratomi wrote:
>
> Hi all-
&
t 11:21 PM Toshio Kuratomi wrote:
>
> Hi all-
>
> For all those wanting to test the next version of Ansible, we're happy
> to announce that Ansible 2.10.0 beta1 is now available on PyPI!
>
> Ansible 2.10.0b1 pulls in the ansible-base-2.10.1 (presently rc2)
> package v
ode.net/kb/answer/registration I highly recommend
registering and testing that you are able to participate in
#ansible-community discussions before the meeting on the 17th!
-Toshio
On Thu, Sep 10, 2020 at 8:29 AM Toshio Kuratomi wrote:
>
> Howdy folks!
>
> We're entering the final
ou aren't sure where your bug falls, pick which you feel is
closest and the Community Team will always move it if needed.
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this g
om/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, se
#x27;re in the
early stages of discussion.
Porting Help
-
There's a unified porting guide for collections which have opted-in.
You can find that at:
https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst
Thanks!
-Toshio Kuratomi
--
ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to a
at 4:42 PM Toshio Kuratomi wrote:
>
> Hi all-
>
> We're happy to announce that the ansible-2.10.2 package is now
> available! This update contains bugfixes and new, backwards
> compatible features in the contained collections as well as bringing
> in ansible-base-2.10.3 as
ible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst
Thanks!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
Hi all,
We're happy to announce that the ansible-2.10.6 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.
Ansible-2.10.x is a big change in how the Ansible package is built so
if you missed out on all the changes that have
Hi all,
We're happy to announce that the ansible-3.0.0 beta1 package is now
available! This update is based on the ansible-base-2.10.x package
just like ansible-2.10 was so the changes shouldn't be too major.
However, it does contain new major versions of many collections which
means that there wi
Hi all,
We're happy to announce that the ansible-2.10.7 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.
Ansible-2.10.x is a big change in how the Ansible package is built so
if you missed out on all the changes that have
Small correction. The pip install instructions should read:
$ pip uninstall ansible
$ pip install ansible==2.10.7 --user
Thanks!
-Toshio
On Tue, Feb 9, 2021 at 1:28 PM Toshio Kuratomi wrote:
>
> Hi all,
>
> We're happy to announce that the ansible-2.10.7 package is now
ocs/docsite/rst/porting_guides/porting_guide_3.rst
Thanks for testing!
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansibl
ra days so at yesterday's Community IRC meeting we voted to allow a
slip to Thursday, February, 18th if we needed it.
I just didn't want anyone to be surprised if Ansible-3.0.0 shows up a
few days late!
Thanks,
-Toshio
On Tue, Feb 9, 2021 at 3:59 PM Toshio Kuratomi wrote:
>
>
Hi all,
We're happy to announce that the ansible-3.0.0 package is now
available! This update is based on the ansible-base-2.10.x package
just like ansible-2.10 was so the changes shouldn't be too major.
However, it does contain new major versions of many collections which
means that there will be
Hi all,
We're happy to announce that the ansible-3.1.0 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.
If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the backgro
eenode.net
Porting Help
-
A unified porting guide for collections which have opted-in is being
worked on. For now, you can find it in this pull request:
https://github.com/ansible/ansible/pull/73930
-Toshio Kuratomi
P.S. Many thanks to felixfontein for doing most of the work to up
Hi all,
We're happy to announce that the Ansible-4.0.0 alpha2 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-core-2.10.x). There may be backwards
incompatibilities in the core play
Hi all,
We're happy to announce that the ansible-3.2.0 package is now
available! This update contains bugfixes and new, backwards compatible
features in the contained collections.
If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the backgro
Hi all,
We're happy to announce that the Ansible-4.0.0 alpha3 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-base-2.10.x). There may be backwards
incompatibilities in the core play
Hi all,
We're happy to announce that the Ansible-4.0.0 alpha4 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-base-2.10.x). There may be backwards
incompatibilities in the core play
Hi all,
We're happy to announce that the ansible-3.3.0 package was released on
April 20! The update contains bugfixes and new, backwards compatible
features in the contained collections.
If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the
Hi all,
We're happy to announce that the Ansible-4.0.0 beta1 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-base-2.10.x). There may be backwards
incompatibilities in the core playb
Just a brief reminder about the Ansible 3 and 4 schedule:
* The last Ansible 3 release is planned for May 11, 2021
* Ansible 4.0.0 release candidate 1 is also planned for May 11, 2021
* If there are no blocker bugs discovered, Ansible 4.0.0 final will be
made on May 18, 2021
-Toshio
--
You rece
Hi all,
We're happy to announce that the Ansible-4.0.0 beta2 package is now
available! This update is based on the Ansible-core-2.11.x package
which is a major update from the Ansible-3 package (Ansible-3 was
based on Ansible-base-2.10.x). There may be backwards
incompatibilities in the core playb
Hi all,
We're happy to announce that the Ansible-4.0.0 release candidate 1
package is now available! This update is based on the
Ansible-core-2.11.x package which is a major update from the Ansible 3
package (Ansible 3 was based on Ansible-base-2.10.x). There may be
backwards incompatibilities in
Hi all,
We're happy to announce that the ansible-3.4.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
If you would like to learn about how and why we got to version 3.0.0,
we invite you to visit our blog for the backgro
log/ansible-3.0.0-qa
Porting Help
-
A unified porting guide for collections which have opted-in is
available here:
https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_4.html
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"An
Hi all,
We're happy to announce that the ansible-4.1.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
How to get it
-
Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need t
Hi all,
We're happy to announce that the ansible-4.2.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
How to get it
-
Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need t
Hi all,
We're happy to announce that the ansible-4.3.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
How to get it
-
Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need t
Hi all,
We're happy to announce that the ansible-4.4.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
How to get it
-
Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need t
Hi all,
We're happy to announce that the ansible-4.5.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
How to get it
-
Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need t
Hi all,
We're happy to announce that the ansible-4.6.0 package has been
released! The update contains bugfixes and new, backwards compatible
features in the contained collections.
How to get it
-
Due to a limitation in pip, if you are upgrading from Ansible 3 (or
earlier), you need t
Hi all,
We're happy to announce that the Ansible 5.0.0 alpha1 package is now
available! This update is based on the ansible-core-2.12.x package
which is a major update from the one used by Ansible 4. Ansible 4 was
based on Ansible Core 2.11.x. There may be backwards incompatibilities
in the core
uri should work and I can help diagnose that. What are you sending to it
and what's the error message?
-Toshio
On Fri, May 6, 2016 at 11:10 AM, 'jhawkesworth' via Ansible Development <
ansible-devel@googlegroups.com> wrote:
> Interesting, I'm trying to do something similar with ansible 2.0.0.
On Mon, May 9, 2016 at 5:21 AM, Frank Van Tol
wrote:
> No, the check is correct, the policy string must start with a {
>
> One can easily confirm this in the AWS Console.
>
> The string that is sent to AWS probably needs to start with a "{" but the
ansible module should be able to take the user i
On Thu, May 5, 2016 at 7:31 AM, Brian Coca wrote:
>
> - in all versions of Ansible, put in a preceding space " {{lookup... ",
> this will skip type detection.
> - in the latest versions a `|to_json` and certain other filters at the
> end will also bypass the automatic type casting.
>
> Note o
For people experiencing this, can you test out:
https://github.com/ansible/ansible-modules-extras/pull/2126 need to know if
that's sufficient or if there's more code needed to fix this. Also need to
know if there's any regressions introduced by it.
-Toshio
On Mon, May 9, 2016 at
We're slowly moving to the place where modules are usable on python3 as
well as python2. This is not likely to be reliably usable by 2.2 but you'll
start to see a few modules that you can use on py3 when we release.
As a first step we're starting to get modules to syntax compile with
python3 as we
Just an update for the mailing list -- we finished reviewing and merging
this too late for 2.1.0 but it is now merged into the stable-2.1 branch
for inclusion into 2.1.1.
-Toshio
On Mon, May 23, 2016 at 7:23 AM, Bernhard L. wrote:
> Hi,
>>
>>
> It would be nice if this issue
> https://github.c
Greetings all,
For 2.2 we're making a change to when Ansible sets the LC_ALL and LANG
environment variablesfor running modules. Here's what that means for you:
Executive summary for users:
If you notice Ansible modules in devel throwing errors because the module
is not finding a string it expe
ir
OS/distribution or on how they can install and support a newer version of
Python on their older machines.
Thanks,
-Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails f
Hey everyone, just dropping a short status update on the progress on getting
Ansible running on python3.
Bad news first: I don't think that Ansible-2.2 on python3 will be production
ready. There are large pieces of the controller side code that I haven't yet
looked at or tested heavily and the f
Greetings all, just writing to let you all know the present status of
repomerge and a problem that we have encountered that you're likely to run
into later as well.
== Executive summary ==
* We probably have to rewrite git history to fix problems caused by the
repomerge script. This will break ex
An Ansible AWS SIG was recently formed. If you are on IRC, they have a
channel on irc.freenode.net: #ansible-aws.
I've mentioned the PR there as well but it's always better if the PR
submitter shows up to ask for review and respond to any requests for
changes.
-Toshio
On Thu, Aug 3, 2017 at 9:4
Joining us on irc is the best way. #ansible-devel on irc.freenode.net
We get so many issues and PRs that we have a very large backlog. Showing
up and being interested in the process of review and fix is the best way to
get something merged quicker.
Depending on what it is, having other people w
build your own .tar.gz (output will be dist/ansible-2.4.0.0.tar.gz):
$ make sdist
If you discover any errors, or if you see any regressions from
playbooks which work on 2.3.x and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.
Thank
re to mention you're testing against this release candidate.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible
o test our release
process with the updated documentation rather than to get additional
testing as rc4 should be equivalent to rc5 in terms of code.
I'll send out an update in the rc4 or rc5 release announcement if any
of these plans change.
Thanks!
Toshio Kuratomi
--
You received this m
On Wed, Sep 13, 2017 at 3:50 PM, Toshio Kuratomi wrote:
> Note that we're still on track for final release on the 19th. Towards
> that end we're planning on having one more rc with code changes on
> Saturday, the 16th. Unless blocker regressions are found, the code
> c
f you see any regressions from
playbooks which work on 2.3.x and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Develop
with 2-3 being betas containing additional bugfixes
followed by one (or more if really needed) release candidates. The
target is to have 2.4.1 out roughly a month after 2.4.0.
Thanks for testing!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"
Hi all, we're happy to announce that Beta 2 for 2.4.1 is now available
for testing.
How do you get it?
--
The tar.gz of the release can be found here:
https://releases.ansible.com/ansible/ansible-2.4.1.0-0.2.beta2.tar.gz
SHA256:
ocker bugs are discovered in this release candidate, 2.4.1
final will be out next week.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from i
these changes only affect running our test
infrastructure, not the code used at runtime by end users, I'm not
anticipating pushing an rc2 for these changes.
I'l update the list if any blocking bugs are found which will require an rc2.
-Toshio
On Wed, Oct 11, 2017 at 10:45 PM, Toshio Kuratomi
I believe there is a bug for this open[1]_. If you change remote_tmp
to use $HOME instead of ~ I believe that workaround will fix your
issue on Solaris (but may introduce a problem on platforms where the
HOME environment variable is not set). The problem ultimately comes
down to Solaris 10 not sh
I have bash on the Solaris box, so I may try the
> ansible_shell_executable.
>
> Looking forward to the 2.5 release so I can set it fine grained. These
> global config changes concern me given the size and growth of our ansible
> deployment env.
>
> On Thursday, October
build your own .tar.gz (output will be dist/ansible-2.3.3.0.tar.gz):
$ make sdist
If you discover any errors, or if you see any regressions from
playbooks which work on 2.3.2 and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.
Thank
release blocker. So we've merged a fix
for that and released 2.4.1.0-rc2 today. If no further blockers are
discovered, we'll release 2.4.1 final next week.
.. _[1]: https://github.com/ansible/ansible/issues/31857
Thanks!
Toshio Kuratomi
--
You received this message because you are
ryansb and sivel commented on your question onIRC but it sounds like
you'd already left for the day. Here's what they said:
Good afternoon! I was wondering if someone could provide
guidance on a design decision within the
digital_ocean_domain module. I'm currently working with Akasurde to
remove
few days. So today I've been merging the
fixes that accumulated over the past few weeks of waiting for the
release candidate to turn into final and put them into a beta tarball
for everyone to start testing and finding the blocker bugs early so
that we can have a solid 2.4.2 release.
T
* November 15th: Beta4
* November 22nd: Rc1
* November 29th: 2.4.2 final
These dates could still be adjusted to try to work around Thanksgiving
better and of course, if blockers are found in RC1 we'll have to slip
into December for the final release.
Thanks!
Toshio Kuratomi
--
You received
On Nov 2, 2017 6:22 AM, "Tejas Gadaria" wrote:
Hello All,
I have a shell script say 'test1.sh', roughly looks like this,
I am trying to execute script with ansible, which throws "No such file or
directory" error for "source ../Properties/Main.sh"
However, the script is working fine is I am NOT u
uncement:
15th November - 2.4.2-beta4
22nd November - 2.4.2-rc1
29th November - 2.4.2 final
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails f
Hi all, we're happy to announce that beta4 for 2.4.2 is now available
for testing.
How do you get it?
--
The tar.gz of the release can be found here:
https://releases.ansible.com/ansible/ansible-2.4.2.0-0.4.beta4.tar.gz
SHA256:
rk on 2.3.x and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this grou
It should be run from a checkout of the source repository. The dev_guide
documentation anticipate that you are developing ansible and working from a
checkout.
-Toshio
On Nov 26, 2017 11:20 PM, "Jae Kim" wrote:
Some replied "There isn't a file named webdocs, it's just a make target."
Then und
This doesn't seem like it is frozen. How long did you wait for it to
finish? Did your CPU continue to be working hard during this time?
There was a Sphinx version that did get stuck when building docs but in
general, the docs build does take quite a while. It takes over an hour for
me on modern
Hi all, we're happy to announce that Beta1 for 2.4.3 is now available
for testing.
How do you get it?
--
The tar.gz of the release can be found here:
https://releases.ansible.com/ansible/ansible-2.4.3.0-0.1.beta1.tar.gz
SHA256:
Minor correction: If we hit the Final/RC3 date that would be 24th of
January, 2018; not 24th of December.
-Toshio
On Wednesday, December 6, 2017 at 7:54:17 PM UTC-8, Toshio Kuratomi wrote:
>
>
> Tentative release schedule for 2.4.3
>
> Beta1 6 Dec
> Beta2 20 Dec
e.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.com.
For more options, visit https:/
Sigh, Corrected subject as above ;-)
On Wed, Dec 20, 2017 at 2:06 PM, Toshio Kuratomi wrote:
> Hi all, we're happy to announce that Beta 2 for 2.4.3 is now available
> for testing.
>
> How do you get it?
>
This is a good idea. For parsing playbooks we made this change a long time
ago. Could you open a bug report on GitHub for this? With the holiday
vacation coming up, I don't want this to be forgotten.
Thanks,
-Toshio
On Dec 20, 2017 9:08 PM, wrote:
> Hi all,
>
> I'm using ansible to deploy my
ictable schedule.
We will probably switch over to accumulating minor bugfixs in the
stable-2.4 tree and only making a release with them included if a
large enough bug is discovered that warrants a 2.4.5.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Goo
build your own .tar.gz (output will be dist/ansible-2.4.3.0.tar.gz):
$ make sdist
If you discover any errors, or if you see any regressions from
playbooks which work on 2.4.2 and prior, please open a Github issue
and be sure to mention you're testing against this release candidate.
Thank
candidate.
--
The notable changes in this rc are some improvements for speed and
memory when using include_role and some butg fixes for the azure
modules.
If all goes well with testing of this, we should be releasing 2.4.3.0
final next week!
Thank
s
as we're hoping that this will be the last release candidate before
2.4.3.0 final.
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it,
Greetings all,
I just wanted to say a brief word about my intention as the 2.4.x
Ansible Release Manager forgetting 2.4.4 out the door and any further
2.4.x releases after that.
Release Schedule for 2.4.4
==
My plan is for 2.4.4 to be released shortly after 2.5.0 final is
LOG.md#244-dancing-days---tbd
Thanks!
Toshio Kuratomi
--
You received this message because you are subscribed to the Google Groups
"Ansible Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to ansible-devel+unsubscr...@googlegroups.c
ay, February 21, 2018 at 10:55:24 PM UTC-8, Toshio Kuratomi wrote:
>
> Hi all, we're happy to announce that Beta1 for 2.4.4 is now available
> for testing.
>
> How do you get it?
> --
>
> The tar.gz
ary 21, 2018 at 10:55:24 PM UTC-8, Toshio Kuratomi wrote:
>
> Hi all, we're happy to announce that Beta1 for 2.4.4 is now available
> for testing.
>
> How do you get it?
> --
>
> The tar.gz
On Tuesday, February 27, 2018 at 11:16:28 PM UTC-8, Guillem Sola wrote:
>
> Hi,
>
> I'm trying to run some integration tests from ubuntu against a windows10
> host with
>
> ./ansible-test windows-integration -v win_xml --allow-destructive
>
> Test tasks starts but it complains
>
> fatal: [window
candidate.
--
I'm aiming to have 2.4.4 final come out the week after 2.5.0 final is
out. So do test this out if you're intending to stay on 2.4.x a while
longer but note that the final of 2.4.4 won't be released until after
2.5.0.
Thanks!
1 - 100 of 147 matches
Mail list logo
