I’ve noticed that Tower 1.4.5 has already been released http://blog.ansibleworks.com/2014/02/10/tower-1-4-5-formerly-awx-released/, but no ansible yet.
Shouldn’t they be in sync?
If not, when ansible 1.4.5 is going to be available?
Thanks
Stan
I’ve noticed that Tower 1.4.5 has already been released http://blog.ansibleworks.com/2014/02/10/tower-1-4-5-formerly-awx-released/, but no ansible yet.
Shouldn’t they be in sync?
If not, when ansible 1.4.5 is going to be available?
Thanks
Stan
Stan, we are not keeping the core/Tower versions in sync, it’s mainly been coincidental that it’s worked out that way so far. That said, we will probably be releasing an Ansible 1.4.5 in the near future, to address one reported bug.
If you have any further questions, let us know.
Thanks!
Thanks James,
Do you happen to have a kind of release schedule anywhere?
I was trying to google it, all I could find is that 1.5 will be release in March.
Also, are modules (in particular ec2*) get updated within minor releases (1.4.x) or just only within major ones?
Thanks again!
Stan
Hi all,
We do hotfix releases for major bugs only, and they do not include feature updates.
Ansible 1.5 (the next full release) is currently targetted for approximately the end of Feb, so that we can finish up ansible-vault, share it, and get it well tested. We also want to mix in some more merges and bugfixes of course too!
Typically releases fall into a rhythm of about every 2-3 months depending on how many features they contain.
We took a survey about this long ago and folks thought that releasing every month was 2 months, and 2-3 months was about the optimal range for everyone. We shoot for closer to 2 most times but will hold things up when there is a lot of goodness coming in. Last time this was Galaxy, this time it’s vault.
–Michael
Thanks Michael,
That answered my questions.
Can’t wait for 1.5 to be released
Stan
Hi James,
Which Bug? if i am using a couple of days development release,is it fine?
thanks,
walid
There’s a bug on 1.4.5 that deals with handlers always being notified that was introduced via another commit that was pulled into the 1.4.N series, that shouldn’t have been.
Additionally, there’s a permissions correction for a particular module. This will be releasing early this afternoon with a bit more details when we push it.
Slight update – it is just be the latter fix.
The other issue seems to be only on devel, which is good. Which also explains why there was less shouting about it.
Thanks Michael
soo … when is 1.6 being released?
:-p
I will use development until 2.x release is out
I can release version 3000 tomorrow.
Just have to edit the VERSION file and hit “make”