Anton Novikov wrote: > ... > 1. Switch to a distributed revision control(git, mercurial). I myself > switched from > SVN to Mercurial some time ago very easily. It has its advantages(most > evident - local commits). > By the way it's possible to use them simultaneosly and keep in sync.
Last time I checked, neither git nor mercurial works very well on Windows. If you want, you can use svk on top of svn to get local commits/distributed development, and push finalized changes back out to the main repo. > 2. Make a web interface to revision control system. Like: > http://hg.sharesource.org/sharesource/ I'm planning on (finally!) getting viewcvs installed on the current server so we'll have a better web interface to the repository. > 3. Improve bug trackers - add keywords, for ex. to group bugs based on the > subsystem involved This is already supported via the "subsystem" field in the current database, and subsystems can be added by any developer. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
