Sitecore Development / Kim Hornung

Thursday, January 20, 2011

Sitecore releases 6.3.1 (rev. 110112)

Today, Sitecore has released 6.3.1 (rev. 110112), our 4th update for CMS 6.3.

Sitecore 6.3.1 is a regular maintenance update. The version number has been changed from 6.3.0 to 6.3.1 because of some database schema changes in the EventQueue table.

Highlights in this update:
  • The most imporant set of fixes and improvements in this update are related to scaling and multi-instance setups (backported from 6.4.1)
  • Also, this update contains a number of fixes and improvements that were released in 6.2 Update-5 (and which were already merged to 6.4 as part of 6.4.0 Update-1). In other words, all CMS 6.2 updates have now fully been merged to 6.3, including the fixes and improvements to Lucene search.
As always, there's a number of additional fixes and improvements in this update, so be sure to check out the full release notes.

Everything is already available on SDN, including:
  • The release notes which describes the improvements and fixes in this update
  • The update page which contains download links for the full distribution, as well as instructions for updating existing Sitecore solutions to 6.3.1

Updated Scaling Guide
As previously mentioned, we published a new version of the Scaling Guide for CMS 6.3 and 6.4 earlier this month.

If you're planning to implement multi-server setups with Sitecore CMS 6.3 or 6.4, you should make sure to grab a copy of the revised documentation:
http://sdn.sitecore.net/Reference/Sitecore%206/Scaling%20Guide.aspx

SQL Server Replication
And to repeat myself some more: If you are setting up SQL Server Replication, make sure that to check out the updated version of the SQL Server Replication Guide which was published when 6.4.1 was released:
http://sdn.sitecore.net/Reference/Sitecore%206/SQL%20Server%20Replication%20Guide.aspx

The updated documentation contains instructions for configuring SQL Server replication to replicate data in the EventQueue table after data from other tables (it's a simple step, but quite important).

0 Comments:

Post a Comment

Subscribe to Post Comments [Atom]



<< Home