Congratulations! I must say that Fossil is the best thing to happen to my development workflow this year, as I am pretty sure that using Git has resulted in the premature death of too many of my brain cells. I'm glad to be able to replace Git in every place that I possibly can with Fossil.
The occasion of the seven year anniversary reminds me of something I've been meaning to ask on the list. It has been asked in the past according to my check of the archives, but is there any chance you would be willing to go on Floss Weekly and talk about Fossil? I know that you were on there to talk about SQLite quite some time ago, but I would love for there to be a show featuring Fossil. I know that Randal's current way for projects to get on the show is that he will only schedule a time if the project leader(s) contacts him directly. In any case, I hope you will consider going on the show (alone or with another core committer), as it would be a great way to let more people know about the awesomeness that is Fossil. - joe On Fri, Jul 25, 2014 at 11:57 AM, Richard Hipp <d...@sqlite.org> wrote: > The seventh anniversary of the first self-commit of Fossil source code was > this past Monday. Time flies. > > The logical predecessor of Fossil was CVSTrac (http://www.cvstrac.org/) > which was a wiki and trouble-ticket system built atop CVS. CVSTrac became > the inspiration for Trac (http://trac.edgewall.org/wiki/CvsTrac) which is a > similar tool for SVN that became far more popular than CVSTrac and which is > still in active use. Fossil was originally created to provide features > needed in SQLite development, features that I couldn't get with CVS+CVSTrac, > or with Monotone or Git or Mercurial or any other configuration management > system available at the time. I worked on prototypes of Fossil for a year > or more prior to the first self-commit on 2007-07-21, but none of those > early prototypes survive. > > Code archeologists will be able to find a lot of commonality between the > CVSTrac and Fossil source codes. There is a clear genetic relationship > between the two systems. > > Fossil was created for the purpose of aiding in the development of SQLite. > (Other uses for Fossil, though welcomed, are secondary.) The SQLite > documentation sources (http://www.sqlite.org/docsrc/timeline?a=2000-01-01) > were split off from the SQLite source tree in CVS on 2007-11-12, just a few > months after Fossil began self-hosting. But the core SQLite source code did > not move to Fossil until 2009-08-11, just after the release of SQLite > version 3.6.17, over two years after Fossil became self-hosting. The move > from CVS to Fossil has proven to be a boon for SQLite development. > > CVSTrac was in active use by SQLite for a little over 7 years. To my > knowledge, nobody uses CVSTrac any more. (OpenSSL was the last known user > of CVSTrac and they switched over to Git at the beginning of 2013.) Fossil > will soon overtake CVSTrac in terms of years of use, and Fossil has a great > deal more momentum and a much larger user base than CVSTrac ever had. > > -- > D. Richard Hipp > d...@sqlite.org > > _______________________________________________ > fossil-users mailing list > email@example.com > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > _______________________________________________ fossil-users mailing list firstname.lastname@example.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users