Introduction
The current trunk has been branched to "opennode2-google-net/branches/v1.1.12" in prep for a significant new source code release of v1.2 in the next couple weeks.
Details
If you would like to continue using the older v1.1.12 of OpenNode2, check out from the branch and work on the source code from there. The new v1.2 will have some source code structural changes, along with normal bug fixes and enhancements. Initial checkins for v1.2 will begin next week (1\17\2011).
Hello, Can the new plugins v1.2 run against the older Node 1.1.13 base or does the Node have to be updated as well?
Thanks
Hi Drew,
The new v1.2 plugins are NOT compatible with the version 1.1.13 Node, as there have been substantial modifications and improvements under the hood. Luckily, however, the Node upgrade process should be as simple as overwriting your existing Node binaries with the new ones. There have not been any changes to the Node metadata database, for example.
Just FYI: The new v1.2 Node has not been released yet, we are still in the middle of testing. There will be an announcement when it is released, probably within the next couple weeks.
Thank you Ted for the quick response, that makes sense. Secondary question, to move the site to a different server, do you need to reinstall the plugins or can you copy the site and db? Is there any registration of the dlls that occurs during the upload?
Thanks, Drew
Hi Drew, Moving the Node from one server to another is as simple as copying the OpenNode2? folder from one server to another. Of course, you will need to update any folder path references in Deployment.config to reference the new folder location (if it changes), and you will need to update the server url/ip references to the new server location in Deployment.config, as well. Copying the database should work, as well, since there are no machine-specific settings in the database. All-in-all, we've tried to make the update/migration process as simple as possible for both us and end users.
will there be a similar new source code release for the Java version of OpenNode2?, or only DotNet??
Hi Julia,
We are planning on releasing a new version of the Java node within the next two months. The newest version will incorporate the interoperability fixes that are currently under discussion by EN governance along with some minor functional improvements to the Admin utility. It will be necessary to upgrade all plugins, but that should only require that the newest version be uploaded via the Admin utility.
A branch was created for v1.2.2 of the .NET OpenNode2? code:
https://opennode2.googlecode.com/svn/branches/dotnet/v1.2.2
This is a stable branch that can be used for current .NET OpenNode2? development. The .NET trunk will be updated over the next few months with code for the version 2.0 release of OpenNode2?. We will notify and branch when the v2.0 code is stable, tested, and ready for general release.
So, for now, if you would like to do active development with the .NET code, use the v1.2.2 branch, not the trunk.