After this upgrade we start a new stage in Likindoy looking forward for: stability, simplicity, translation to English and we start working on compatibility with Python 2.6 and future Python 3.

Soon we will transfer testing version to stable since the unstable version (the one we work everyday) has been tested for longer than 2 months without detecting any important issue.

Also because the filosophy of the project, we are thinking to remove testing branch, because unstable branch is usually newer and less buggy, and also is our real testing version. Maybe we will end up showing on the website frozen versions of the project, what do you think?.

Right now on the repository you will find:

• stable: the version of Likindoy that is working in our systems right now.
  
  
• testing: the new version of Likindoy that we are working on and that is completely new.
  
  
• Other branches: are holding diferent developments that will be merged onto 'testing'.
  
  

After talking a lot about keep working with Subversion or migrating to GIT/Bazaar, we have decided to move forward to Bazaar because it is easier to use than GIT. Also we defined a new more colaborative model of working, that divides Likindoy's development in 3 levels, all of them public and separed in the next versions:

• stable: it will be upgraded slowly and its target will be to provide a very stable version of Likindoy that has been tested for a long time, the only problem of this version is that will be always an old version.
  
  
• testing: it will be Likindoy's version that will provide the lasts upgrades that we are working on, we will try to keep stable this version, but never will be so much tested as the 'stable' version.
  
  
• unstable: each Likindoy's developer will have an unstable version with its own and particular development, when some branch is finished it will merge over 'testing'.
  
  

We made two formats, one is thought to be easy for downloading (Spanish) and the other for online reading (Spanish).

The bug affect to all users that were managing Likindoy from a shell not connected to a graphic enviroment, the installer tried to print more than 80 columns in the string. This was produccing an exception that did not allow to continue the process.

We have been using for a several months the ODS support to manage signals throught a spreadsheet in Open Document Spreadsheet format. From the last summer we have been using the management throught ODS because we needed to process many singals and that was taking too much time for managing in a plain text file.

In addition we also repaired a bug with PESYR RTUs that in older versions of PESYR, when sincronizing the time of the RTU required to say which year has 29 days in february and which not, but this is not necesary anymore in new versions and now we do not need to send this information to this RTUs.

The development team has been working for longer than two years to get this version stable. We added many new features specially in specialized modules from diferent hardware.