> I am upgrading from 2.0.0 to 2.1 to test out some of the new features. > Should this be done manually ? Any caveats I should know about? I > remember reading a user’s e-mail on an issue he was having and I can’t > seem to find the e-mail thread.
2.1.0 has Avaya/Nortel regressions that are now fixed in the current development tree. You can also find a fix in the issue tracker that is easy to apply to 2.1.0. The Meru module was also renamed in the 2.1.0 cycle and unfortunately the web admin still refers to the old name. It is fixed in current development tree. At this rate, we will have a 2.2.0 within the next couple of weeks with another load of features and fixes.. So depending on if you can or can't wait you might want to hold the upgrade for now. Cheers! -- Olivier Bilodeau [email protected] :: +1.514.447.4918 *115 :: www.inverse.ca Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ Enable your software for Intel(R) Active Management Technology to meet the growing manageability and security demands of your customers. Businesses are taking advantage of Intel(R) vPro (TM) technology - will your software be a part of the solution? Download the Intel(R) Manageability Checker today! http://p.sf.net/sfu/intel-dev2devmar _______________________________________________ Packetfence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
