Hi fellow eBox users!
Allow me to break the exciting news to you: our first release candidate for 1.4 is already available. Freshly baked and ready to
download. Remember that our beta 1.3.x releases have finally become this release candidate.
In this release candidate the focus has been on making migrations work from 1.2 to 1.4. We have detected a very few rough edges that will be fixed for 1.4. We are almost there and that's why we want you to try and test this release candidate.
The installer of this release ships a new cool feature. It allows you to install and automatically boot a local browser and a console to manage eBox locally.
UpgradingPlease note that this is a release candidate, it's not production ready yet but very close. The upgrading process might have some rough edges and that's where your testing can help to make 1.4 a great release.
The supported migration path is from eBox 1.2.x to 1.4. The modules that have changed the most are the LDAP based modules.
Although we have tested thoroughly several upgrading scenarios, do not upgrade your production machine if you are not ready to roll back the changes very quickly in case things go wrong. We strongly recommend you make use of common sense and proceed with caution. Always backup your system. We encourage you to use a virtual machine to install or upgrade to 1.4 your current configuration. Check that everything is working as expected. And then proceed with the actual upgrade.
Please pay special attention to Samba and Asterisk. eBox 1.4 ships a new version of these packages. Again, use common sense, and test that there is not any regression with the feature set you use.
Known issuesWe recommend you upgrade the machine locally, especially, if you are upgrading a machine with a DHCP configured interface. As you might lose your gateway during the process. Running "sudo /etc/init.d/ebox network restart" will bring the gateway back.