Probably they consider this concern non-relevant, as it was first detected and reported some months ago and it still remains unclear and undocumented.
For me, it's crucial to have a public access to the source of an Open Source product. And in this case, as Alfresco 5.x is going to be used during several years, moving out of the main scope the source code for these releases seems a bad decision.
It is, and has always been, absolutely clear and well documented: Our Subversion server is the only source of truth for Legacy Source Code.
The mirrors community-edition-old and share-old on GitHub have only been inofficial, unsupported mirrors of our official Subversion server.
For me, it's crucial to have a public access to the source of an Open Source product.
...moving out of the main scope the source code for these releases seems a bad decision.
The source code has always been in our Subversion server and continues to be there.
Our Subversion server has always been the only source of truth for our source code. After officially moving to Git, our Subversion server stays the only source of truth for the code until our move to Git.
Yes. It contains all the community source code until we moved to Git. After moving to Git, we also split up the monolithic code base into separate projects. You can find the latest code of these projects in our organisation on GitHub.