1 week vacation pause after just released 2.2c
Posted: Fri Mar 28, 2008 3:53 am
Hi,
I will be out on vacation for one week, starting this saturday.
I tried hard to fix most of the reported major bugs before leaving. 2.2b and 2.2c are just out to go improve on this.
Please allow me two remarks:
1) When drilling down on reported bugs I often found the situation that user are installing 2.1 and 2.2 software versions on 2.0x systems. As we have a change in kernel versions between 2.0 and 2.1 this is not intended to work. Please make use of the documents in the download section that guide you how to migrate from 2.0d to newer versions:
http://www.meteohub.de/joomla/index.php ... &Itemid=29
The migration to 2.1/2.2 cannot be done by simply doing a web install. Once have done the step to the new kernel future updates again go with the easy web-based install.
2) I often read about downgrading to older sw versions. This also is not intended to work. May be you are lucky and it does, but I can hardly imagine what this does to changes of configuration files etc. I try to solve reported bugs fast, so it might be the better way to stay with the bug in the new version for a moment and to get it solved with the next updates... updates are coming very often, as you know.
3) After an update, power on, change in sensor setup, etc. Meteohub has to do a complete recomputation on time compacted data. As your amount of data is starting to grow you should give meteohub some time to get all data in good shape according to the done changes. This is a one time effect, during normal operation these tasks run as incremental jobs seamless in the background. However, before you report bad sensor data, not working graphs etc, please make sure that your system is not just reconstructing the needed data. Meteohub's system information pages gives information if these recomputation jobs are running.
During next week I will not be able to answer mails or read the forum. So please help each other . I will jump in again, the moment I am back. Thanks for your understanding!
I will be out on vacation for one week, starting this saturday.
I tried hard to fix most of the reported major bugs before leaving. 2.2b and 2.2c are just out to go improve on this.
Please allow me two remarks:
1) When drilling down on reported bugs I often found the situation that user are installing 2.1 and 2.2 software versions on 2.0x systems. As we have a change in kernel versions between 2.0 and 2.1 this is not intended to work. Please make use of the documents in the download section that guide you how to migrate from 2.0d to newer versions:
http://www.meteohub.de/joomla/index.php ... &Itemid=29
The migration to 2.1/2.2 cannot be done by simply doing a web install. Once have done the step to the new kernel future updates again go with the easy web-based install.
2) I often read about downgrading to older sw versions. This also is not intended to work. May be you are lucky and it does, but I can hardly imagine what this does to changes of configuration files etc. I try to solve reported bugs fast, so it might be the better way to stay with the bug in the new version for a moment and to get it solved with the next updates... updates are coming very often, as you know.
3) After an update, power on, change in sensor setup, etc. Meteohub has to do a complete recomputation on time compacted data. As your amount of data is starting to grow you should give meteohub some time to get all data in good shape according to the done changes. This is a one time effect, during normal operation these tasks run as incremental jobs seamless in the background. However, before you report bad sensor data, not working graphs etc, please make sure that your system is not just reconstructing the needed data. Meteohub's system information pages gives information if these recomputation jobs are running.
During next week I will not be able to answer mails or read the forum. So please help each other . I will jump in again, the moment I am back. Thanks for your understanding!