fu created at Sunday, 2012-03-11, 08:03:49
2 Replies, 1746 Hits
Fossil is a very interesting distributed version control system I found from Lua mailing list recently. It has a number of nice features, including integrated bug tracking and wiki system, autosync mode, self-contained source codes and executable, SQLite database storage and easy use etc.
After some trying, I am convinced that it should be a good idea to switch to use Fossil for version control and host Dao project repositories on daovm.net . Having an integrated bug tracking and wiki system in Fossil, makes it a quite natural choice to host the repositories on this site without the trouble of using other code hosting sites. It have been suggested to have A central place for dao code-snippets, examples or small modules , Fossil seems to be a simple solution for this. Having the website and Dao project repositories hosted on the same server, a number of interesting things could be done, such as extract and display information from the repositories, or storing site data to an repository etc.
For Dao projects, I am considering to make some minor adjusts and organize them in the following way:
The current dao repository hosted at dao.googlecode.com will be divided into dao , dao-modules (for modules DaoCXX, DaoJIT, graph, net, os, stream, string, sync, web) and dao-tools (for ClangDao etc.).
Pompei2 commented at Tuesday, 2012-05-08, 08:46:02
If I understand it correctly, you want to completely switch? If so then:
fu commented at Tuesday, 2012-05-08, 22:38:26
Not completely, but mostly. New revisions will be regularly pushed to the repository on google code (maybe also github), so that people who don't want to use fossil can also get updated codes. Also it could serve as the principle or backup download archive.
I agree those links should be removed from those prominent places. They can be moved to somewhere in the download page.
New bug reports should be submitted to the fossil ticket system, I will make it clear on the webpages. The one on google code will be disabled after all the issues there have been properly closed (it will take a while).
fu: Dao has finally become feature complete! After the recent implementation of communication channel for tasklets, deferred blocks and exception ... (May.18,05:46)
fu: A new feature for concurrent programming: tasklet communication channels! I have been looking for ways to improve Dao's support for concurrent programming. The most recent imp ... (May.18,00:35)
fu: Dao now supports Go-style panic/exception handling! I recently looked into the panic/ exception handling in the Go programming language (defer- recover), ... (May.07,02:04)