I am happy to announce the first parallel/synchronized release of:
There are a _lot_ of new, big features and fixes in all these packages, but in this announcement, I won't go into that, but:
- parallel/synchronized releases and calver
We have moved all of above projects to calendar versioning, so v17.5.1 means the first patch release in May 2017.
The version numbers of the different Autobahns had become increasingly meaningless, and by using the same, consistent calendar based versioning scheme, you immediately see how old a package is, and whether it "fits" the other packages you might run together.
We've put a lot of effort into testing, in particular integration testing between Autobahns and with Crossbar.io.
So this is a focus of doing parallel/synchronized releases: increase trust in that all the different wheels actually work together.
Which is part of the bigger phase we're moving to: making Crossbar.io and Autobahn even more dependable, and robust for critical production applications and infrastructure.
Sidenote: above scheme will also be used for the revamped AutobahnJava (formerly AutobahnAndroid), and the planned AutobahnC as well.
You can get above software over the established channels (like PyPI for Python etc), but I am also quite proud that we now have a complete set of Docker images for everything above - on 3 CPU architectures!
Over 50 Docker images:
Getting build automation for this working was quite time consuming, in particular making sure it works on all CPU archs:
x86-64 -> obvious general use
armhf -> this is ARMv7, like on the Pi
aarch64 -> this is cutting edge 64 bit ARMv8, like Cavium Thunder-X!!
Eg here is "crossbar version" over different archs:
Note the "Machine" description there.
As you might read between the lines, we are quite bullish on Docker as a publication channel, for development and for deployment.
Publishing Docker images allows us to provide bit-exact software to users, directly, without distro maintainers fiddling ("vendor publishing", "upstream publishing").
It cuts down on support issues: yes, we do support a lot of OSs, run-times, whatnot .. and we will continue to do so.
But the main officially supported publication format is now Docker.
We also provide some first docs for developers that want to use a Docker based workflow:
Have a look at the ascineema videos .. I think this shows how easy it is to create WAMP components in different languages - with no installation pains whatsoever!
The efforts of pulling all of above have become quite big, so if you'd like to help, highly welcome! Testing, docs, code, critics, ramblings;) What you like.