4.2.d Community Edition

[kevinr]

Alfresco 4.2.d Community Edition is now available for download: https://wiki.alfresco.com/wiki/Community_file_list_4.2.d

This release has bug fixes and some/improved features: http://blogs.alfresco.com/wp/kevinr/2013/08/22/alfresco-community-4-2-d

You can read the release notes here: https://wiki.alfresco.com/wiki/Alfresco_Community_4.2.d_Release_Notes
Public SVN revision number for Alfresco Community 4.2.d is 54671 and is tagged COMMUNITYTAGS/V4.2d

Please try out this release and let us know what you think. If you find something you think is a bug, check the list of known issues first before reporting it in the forums or in JIRA.

If you have questions, comments, or general feedback on the release, please create it as a new topic in the appropriate forum.

Enjoy!

Kevin

[cbutters]

Awesome! Thanks for the release!

[pjy]

Hi Kevin,

I have just installed 4.2.d (Centos XXX, Postgresql 9.2.4, tomcat 7, latest java 7) and wanted to migrate our 4.2.c (Centos XXX, Postgresql 8.4.7, tomcat 7, latest java 7) database to the new install. Unfortunately I have not been able to do this ending up with database schema errors. I have followed the standard instructions of dumping the old psql db (pg_dump) and saving the solr dirs (contentstore, contentstore.deleted, solr/archive and sold/workspace) but this causes failures during startup:

2013-10-10 11:28:24,438  WARN  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema validation found 15 potential problems, results written to: /opt/alfresco-4.2.d/tomcat/temp/Alfresco/Alfresco-PostgreSQLDialect-Validation-Pre-Upgrade-alf_-5914354826176335695.txt
2013-10-10 11:28:25,072  WARN  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema validation found 3 potential problems, results written to: /opt/alfresco-4.2.d/tomcat/temp/Alfresco/Alfresco-PostgreSQLDialect-Validation-Pre-Upgrade-avm_-5860163481921594900.txt
2013-10-10 11:28:28,592  INFO  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Compared database schema with reference schema (all OK): class path resource [alfresco/dbscripts/create/org.hibernate.dialect.PostgreSQLDialect/Schema-Reference-JBPM.xml]
2013-10-10 11:28:31,026  WARN  [domain.schema.SchemaBootstrap] [localhost-startStop-1] Schema validation found 23 potential problems, results written to: /opt/alfresco-4.2.d/tomcat/temp/Alfresco/Alfresco-PostgreSQLDialect-Validation-Pre-Upgrade-act_-5943641251513872195.txt

and then a bit further on:

2013-10-10 11:28:54,356  ERROR [solr.tracker.CoreTracker] [SolrTrackerScheduler_Worker-3] Tracking failed
org.alfresco.error.AlfrescoRuntimeException: 09100000 GetModelsDiff return status is 404
   at org.alfresco.solr.client.SOLRAPIClient.getModelsDiff(SOLRAPIClient.java:1059)
   at org.alfresco.solr.tracker.CoreTracker.trackModels(CoreTracker.java:1876)
   at org.alfresco.solr.tracker.CoreTracker.trackRepository(CoreTracker.java:1206)
   at org.alfresco.solr.tracker.CoreTracker.updateIndex(CoreTracker.java:492)
   at org.alfresco.solr.tracker.CoreTrackerJob.execute(CoreTrackerJob.java:45)
   at org.quartz.core.JobRunShell.run(JobRunShell.java:216)
   at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:563)

I have also tried following the instructions posted by Zannafar on the forum thread https://forums.alfresco.com/forum/installation-upgrades-configuration-integration/installation-upgra... but I still can't get it to work. (and I don't understand those instructions anyway….).

Surely this would be a standard thing to want to do - ie upgrade from 4.2.c to 4.2.d and preserve the old 4.2.c data? Are there specific 42c-42d migration instructions I have missed somehow? Is the change from psql 8.4 to psql 9.2 complicating things for me?

Thanks, Peter

[pjy]

Oops - I meant to add the Centos version to my last post - it is 6.4…

[mikel_asla1]

I'll like to understand the Community versions publishing process. Maybe i missed something but 4.2.c was published on december 2012. After that, versión 4.2.d was published 2 months ago, now there is a new release 4.2.e which was published 15 days ago. Is something wrong with 4.2.c? why new version so quick?

[resplin]

Community Edition releases are cut when the engineering team needs feedback on the source tree. Enterprise Edition releases are designed around a more predictable cadence.

Community Edition releases are more frequent when we are testing HEAD before branching for an Enterprise Release. Each release contains additional bug fixes. 4.2.e is very similar to the 4.2.0 release, and now QA will focus on the Enterprise branch. Once the team is ready to start working on 4.3, those fixes will be pushed back to HEAD and a new Community Edition release will be cut with the features slated for that next version.

[mrogers]

Its a bit more positive than that.  Community releases are made when there's something good enough to release.  The reasons for a community release will be explained as above and on the release note.