Releases: eclipse-ditto/ditto
0.8.0
First official release of Eclipse Ditto.
For the full release notes, have a look here: 0.8.0 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Release can simply be started by docker-compose up -d
in "deployment/docker" directory.
0.8.0-M3
Next milestone release of Eclipse Ditto.
The main changes and new features are:
- speed up of search index creation
- applying enforcement of messages received via connections (e.g. from Eclipse Hono)
- copying already existing policies when creating things
For the full release notes, have a look here: 0.8.0-M3 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Milestone can simply be started by docker-compose up -d
in "deployment/docker" directory.
0.8.0-M2
Next milestone release of Eclipse Ditto.
For the full release notes, have a look here: 0.8.0-M2 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Unfortunately, we had some problems during the milestone release build causing that the released artifacts have version 0.8.0-M2b
instead of 0.8.0-M2
.
Milestone can simply be started by docker-compose up -d
in "deployment/docker" directory.
0.8.0-M1
Milestone release of Eclipse Ditto - the first working towards a 0.8.0 release.
- adds support for being deployed into a Kubernetes cluster
- report application metrics to Prometheus
- memory consumption improvements
- stabilization of the connectivity to AMQP 1.0 and 0.9.1
For the full release notes, have a look here: 0.8.0-M1 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
0.3.0-M2
Next milestone release of Eclipse Ditto.
Fixes performance problems in Ditto cluster + stabilized cluster bootstrap.
For the full release notes, have a look here: 0.3.0-M2 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Milestone can simply be started by docker-compose up -d
in "docker" directory.
0.3.0-M1
Next milestone release of Eclipse Ditto.
We renamed the "amqp-bridge" to "connectivity" and therefore also the docker artifact.
The Ditto Docker images now run in the Eclipse OpenJ9 JVM which reduces memory footprint a lot.
For the full release notes, have a look here: 0.3.0-M1 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Milestone can simply be started by docker-compose up -d
in "docker" directory.
0.2.0-M1
Next milestone release of Eclipse Ditto.
For the release notes, have a look here: 0.2.0-M1 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Milestone can simply be started by docker-compose up -d
in "docker" directory.
0.1.0-M3
Second milestone release of Eclipse Ditto.
For the release notes, have a look here: 0.1.0-M3 release notes
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
- eclipse/ditto-policies
- eclipse/ditto-things
- eclipse/ditto-things-search
- eclipse/ditto-gateway
- eclipse/ditto-amqp-bridge
Milestone can simply be started by docker-compose up -d
in "docker" directory.
0.1.0-M1
First milestone release of Eclipse Ditto.
- Java artifacts were deployed to Maven central
- Docker images were pushed to Docker Hub
Milestone can simply be started by docker-compose up -d
in "docker" directory.