Switched completely to JDeb & RPM-Builder to create Debian & RPM files, which should allow to do the complete build on Windows

The artifact names of the products and features have changed to org.eclipse.neoscada and for the deb/RPM packages to neoscada.*

Because of the name changes the release links are broken right now, this will be fixed in the next few days! Also the update
site will not work at the moment, because the composite repository will not be created in the current build - again, reason for this:
all the name changes.

Milestone 0.4.0-M5 features the integration of IEC 60870 and a bit a of refactoring and unit testing around the 60870 server API. While most of the IEC 60870 components
were already part of 0.4.0-M4, this finally brings back the 60870 stack which had to be removed in milestone 0.2.0-M10.

This milestone also cleans up a few leftover issues with re-packaging of Eclipse Neon. Everything should be fine now for a release of 0.4.0.

Again it took us a quite a bit longer than expected, although this
time it was due to scheduling issues. We hope to pick up the pace
with the new releases. In a couple of days the first 0.4 milestone
will be available, but this will only be of interest at first to people
who deploy to RPM based systems.

The 0.3 realease was more or less focused as it turned out to fix
a lot of minor issues and improvement of usability in some corners
of the system.

First of all there is a maintenance release 0.2.2 of the 0.2.x branche, which fixes two issues of the TLS implementation Eclipse NeoSCADA uses for communication. One issue in the NET/GMPP protocol and the other in the NGP protocol. Both issues were found and reported to us by Lorenzo Nicolodi. Thanks!

For the 0.3.0 branch, which is currently in development, the NGP protocol was also fixed. The NET/GMPP protocol however is deprecated and no longer part of Eclipse NeoSCADA starting with 0.3.x. Also does this milestone contain a few other fixes and improvements.

A new name: With release 0.3 Eclipse SCADA will become Eclipse NeoSCADA

In 2013 through the move to the Eclipse foundation, the existing
openSCADA project became Eclipse SCADA. Being a very industrial
oriented project it naturally has a different audience than most other
projects hosted at the Eclipse foundation. The presence there has
encouraged new users to try it out, even if they won't use right now.
Although industrial customers are traditionally very conservative in
their choice of software, and more likely to use systems build by larger
corporations, this is changing right now. Eclipse SCADA for instance, is
now used in three different projects at E.ON. Projects like Eclipse
SCADA are seen as a way to escape vendor lock-in, which has become
stronger and more problematic over the past few years. That in turn means, we
will see more and more of these approaches, also at the Eclipse Foundation.

Over time sometimes adjustments have to be made. Eclipse SCADA is
now on a relatively stable path. That means that the upcoming 0.3
release will not bring a lot new features, but it is focused on
improvements and refinements of the existing system. One big change on
the other hand is the renaming of Eclipse SCADA to Eclipse NeoSCADA,
which became necessary for trademark reasons. It also brings the
naming more in line with the naming policy of other Eclipse projects.
Since SCADA is a very generic term, NeoSCADA will improve the
recognizability as a specific project within and out of the Eclipse
foundation.

For now the new name mostly affects the name of the project itself and
the infrastructure at the Eclipse foundation. New bundles and packages
will get the new name, existing interfaces won't be affected for now.
The goal for the 1.0 release, though, is to have all bundles and
packages renamed to neoscada. The migration path will be outlined in due
time.

We released Eclipse SCADA 0.2.1, which provides a few bug fixes to the 0.2.x release cycle of Eclipse SCADA.

Beside a few issues with the configuration tool and a possible login exception a huge performance improvement on the HD server make up the main parts of this release. Read on for more details. Thanks to everybody who helped with this release!

The first three cover a few oddities with the Eclipse SCADA Configurator tool, especially on Windows. The last issue is a huge performance fix which allows cleaning up
the HD storage pools with a lot less IOs.

The Eclipse IoT working group is currently doing a survey about IoT technologies. As member of the Eclipse IoT working group and top level project, we from Eclipse SCADA would kindly ask
you to give back a few minutes of your time and answer a few questions. This will help make the IoT world a little bit better. Thanks.

It took us a little bit longer than expected, but this was due to the issues with IEC 60870. We had to remove this for the moment and will hopefully provide this
in Eclipse SCADA 0.3.0. In the meantime it is available in openSCADA 1.3, also licensed under the EPL.

So the main new features (besides numerous cleanups, fixes and minor enhancements) are:

The milestone 0.2.0-M10 is a follow up to M9 with the IEC 60870 protocol stack and functionality removed. Hopefully there will be a way to implement
IEC standards in the future at the Eclipse Foundation, but for now it was decided to remove the functionality from Eclipse SCADA and host the development
at openSCADA.org. It still is licensed under the EPL and will still be available
as open source.

On the other hand, this clears the remaining issue before the 0.2.0 release. So with a little bit of luck, the 0.2.0 release will be done before the end of the year.