Is the SVN repository still in use or was it transitioned to something else? The primary users of this SVN repo will be engineers who are not software developers so I think the less complex nature of SVN compared to Git could be a definite advantage. However, I am concerned about the long-term viability of the SVN project because I would like the repo to still be usable by in 5-8 years. Just looking at the development mailing lists, it looks like almost all development has stopped on Subversion which is concerning to me.
Luke > On Oct 28, 2021, at 8:14 AM, Stuempfig, Thomas <thomas.stuemp...@siemens.com> > wrote: > > Hi all, > we had a SVN Repository that served a huge number of PPT Presentations, CAD > Data (MCAD/ECAD), Word. > the repository served over 10 Years of history of ~200 users. > In addition to this, we created useful Web Search Capabilities for PPTs in > the repository on our own based on office and svn api. > (We were able to search for single slides of presentations) > > We even thought of redmine integration in order to track Document Changes > against a Tasks… > > TortoiseSVN was easy enough for the average user and the checked out copy was > really great for us as we travelled a lot during the week. > Check-In and Updates from colleges were done when we had network access. > > The maintenance effort of this Project was really minimal and the effort for > errors / misuse was virtually inexistent. > > > Regards > Thomas > > From: Justin MASSIOT | Zentek <justin.mass...@zentek.fr> > Sent: Donnerstag, 28. Oktober 2021 09:47 > To: Luke Mauldin <lukemaul...@icloud.com> > Cc: Nico Kadel-Garcia <nka...@gmail.com>; Subversion > <users@subversion.apache.org> > Subject: Re: Current project status > > Luke, > > If the 3D models are "source" files, then I personally approve to put those > files into a Subversion repo. That's what I do everyday with Electronic > engineering CAD files. > By the way, don't forget you may not be able to "diff" between two versions > of a file. If not, you lose one the main strength of a Version control > system: doing even a small rollback may become a pain... Plus if you can't > diff, you probably can't merge either! I encourage you to use locks to avoid > any form of conflicts. The "needs-lock" property can be useful. > > As for the project status, I don't know anything but I would be curious to > get the developers' point of view. > > Justin MASSIOT | Zentek > > > On Thu, 28 Oct 2021 at 00:47, Luke Mauldin <lukemaul...@icloud.com > <mailto:lukemaul...@icloud.com>> wrote: > Let me clarify. The binaries can be unity 3d models or other engineering > assets. They are not compiled code. > > > On Oct 27, 2021, at 5:42 PM, Nico Kadel-Garcia <nka...@gmail.com > > <mailto:nka...@gmail.com>> wrote: > > > > On Wed, Oct 27, 2021 at 6:31 PM Luke Mauldin <lukemaul...@icloud.com > > <mailto:lukemaul...@icloud.com>> wrote: > >> > >> We are considering using Subversion for a project with large binary files > >> since it seems to have some strengths in that area compared to the > >> alternatives. But now that the Apache Software Foundation and most other > >> projects such LLVM and FreeBSD have migrated away from Subversion, what > >> does the future of Subversion look like? Is it still being actively worked > >> on? Is anyone sponsoring it? > > > > For me, subversion still has uses by compelling centralized change > > tracking, and by permitting checkouts of very small directories from a > > master repo or a designated tag. > > > > Large binaries..... just don't put those in source control. Put those > > in software packaging. > ----------------- > Siemens Industry Software GmbH; Anschrift: Am Kabellager 9, 51063 Köln; > Gesellschaft mit beschränkter Haftung; Geschäftsführer: Dr. Erich Bürgel, > Alexander Walter; Sitz der Gesellschaft: Köln; Registergericht: Amtsgericht > Köln, HRB 84564; Vorsitzender des Aufsichtsrats: Timo Nentwich >
