Re: SCCS bitkeeper.. check it out?

"Cheng, Cheng-Wei" wrote: > have we consider contact bitkeeper for the source code management 1) why should we change a running system? althoutgh CVS has its problems in some areas i don't see that it is a source of trouble in php or phpdoc developement it is well known to developers, and those who do not know it will have the same problems in getting into any of the alternatives there is a lot of additional tools and documentation available and in use (see for example bonsai.php.net) it has proven over the years that it can do its job sometimes you have to do things in a way that looks complicate or just strange, but it always works as described bitkeeper on the other hand is a new kid on the block, after some noisy announcements in the past it has now finally arrived in silence, there are only a few projects already using it and most of them seem to just have tried it out for a day once especially the one big project it was said to be developed for does (as of now) not use it at all 2) what about aegis then? if we really find that CVS is not good enough for us anymore i'd suggest to have a look at aegis first this one has been in use for years, it is GPLed and it has some features especially interesting for the ongoing QA discussion, especialy : Aegis enforces a development process which requires that change sets ``work'' before they may be integrated into the project baseline. Works includes requiring that change sets build successfully, and (optionally) that they include and pass tests. It also ensures that code reviews have been performed. (this would especially prevent me doing strange things immediatly before a new release is going out, like breaking imap_delete() for 3.0.16 or checking in smtp code for windows from a wrong working directory that doesn't even compile) http://www.canb.auug.org.au/~millerp/aegis/aegis.html > it is free :) well, somehow. to me it looks like neither free spech nor free beer but only like 'you are allowed to have a free beer at home (but close the curtains) or have free beer and speech whenever you show up in our special free pubs ...' i prefer a free system that i may use for commercial developement to instead of a commercial product that is free for free projects but has to be payed for for commercial projects don't get me wrong, this is not about the money or 'free software is more reliable than non-free', it is just that forcing potential developers on a free project into using tools that are not easily capable of general use is a BAD THING (tm), it is a little bit like suggesting to switch the documentation project to StarOffice ... i use it in the company and for private correspondece, i have even bought licenses in the past, but i would never even think about doing public work with it, even with its current 'free' license ... -- Harmut Holzgraefe hholzgra@media-engineering.de