> 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. All right, nevermind. > > 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. Didn't notice that - the subsystem is shown only in roadmap, on "bugs & features" page it isn't
indeed, if we go for reorganization, it would be convenient to have many little subsystems and the code to be split to same-name folders something like: wnd font image threads fs... but the details don't matter it's more interesting what Bill thinks about the idea of merge. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
