3 ms·
If you think that's bad, try looking at the LibreOffice source code. I think I found a 15 year old bug the other day [1] [2], but I only noticed this when I was
by chris_wot 11y ago
If you think that's bad, try looking at the LibreOffice source code. I think I found a 15 year old bug the other day [1] [2], but I only noticed this when I was trawling through the history of the file "outdev3.hxx", which via cgit was a pain in its own right.
There have, in fact, been 5 source code repository switches in LibreOffice over the last 30 years. [3] It started with some sort of proprietary version from 1988 to 2000 so there is no history at all from this period (which I think is a great loss...), from 2000 to 2009 they used CVS, then from 2008 to 2009 they used SVN, then from 2009 to 2011 it was Mercurial, then from 2011 to 2014 it was back to SVN, and LibreOffice started using git from the very start.
One of the worst practices that the OpenOffice.org team had was to get a whole bunch of work, bundle it up into a single commit and then note that there were multiple fixes in the commit. This makes it nigh-on impossible to untangle what fixed what. They apparently branched in SVN, then took the branch and merged it, but then blatted the original branch so now this is all lost in history.
And if you've ever read some of the most crufty parts of LibreOffice (cough VCL cough) then you'd understand that actually reading good commits is really very important for moments you think "what on EARTH is that code doing?!?"...
1. https://bugs.documentfoundation.org/show_bug.cgi?id=96826 https://bugs.documentfoundation.org/show_bug.cgi?id=96826
2. http://randomtechnicalstuff.blogspot.com.au/2016/01/possible-15-year-old-regression.html http://randomtechnicalstuff.blogspot.com.au/2016/01/possible...
3. https://archive.fosdem.org/2014/schedule/event/exploring_openoffice_history_using_git_grafts/ https://archive.fosdem.org/2014/schedule/event/exploring_ope...