Decommissioning of Alfresco SVN Instances

Showing results for 
Search instead for 
Did you mean: 

Decommissioning of Alfresco SVN Instances

Alfresco Employee
1 0 2,291

Dear Hyland Community,

We wanted to take a moment to address the recent decommissioning of the Alfresco SVN instances and provide some clarity on the decision-making process behind this transition.

In recent communications within our organization, it was revealed that the Alfresco SVN instances, including, have been marked as decommissioned. This may have raised questions among our community members, especially those who have been accustomed to utilizing these repositories for their development needs.

The decision to decommission the Alfresco SVN instances was not made lightly but was part of a strategic move towards modernizing our development infrastructure and aligning with industry standards.

Here's a breakdown of the events leading to this decision:

1. Evaluation of Legacy Systems: As part of ongoing efforts to streamline our technical landscape and address technical debt, the Hyland IS team initiated a review of heritage SVN instances, including the Alfresco SVN.

2. Assessment of Usage and Need: Questions were raised regarding the active usage of the SVN instances. Discussions were held internally to determine whether code was still being actively stored in these repositories or if migration to more modern platforms had already occurred.

3. Migration to Modern Repositories: It was confirmed that the repositories had been migrated to a Alfresco GitHub repository.

4. Communication and Transition Plan: While the SVN instances were no longer actively used for development, steps were taken to ensure a smooth transition for our community members. DNS entries were removed, and efforts were made to communicate the decommissioning internally.

5. Future Strategy: With the decommissioning of the SVN instances, our focus now shifts towards supporting and optimizing our existing modern repositories. We remain committed to providing robust development environments that empower our community to innovate and collaborate effectively.

We understand that changes to familiar tools and platforms can sometimes cause uncertainty. However, we believe that this transition ultimately provides greater efficiency, scalability, and alignment with industry standards.

We appreciate your understanding and cooperation as we continue to evolve and improve our development infrastructure. Should you have any questions or concerns regarding this transition, please don't hesitate to reach out to us.

Thank you for your continued support.

About the Author
Angel Borroy is Hyland Developer Evangelist. Over the last 15 years, he has been working as a software architect on Java, BPM, document management and electronic signatures. He has been working with Alfresco during the last years to customize several implementations in large organizations and to provide add-ons to the Community based on Record Management and Electronic Signature. He writes (sometimes) on his personal blog He is (proud) member of the Order of the Bee.