Phade wrote:Yeah, we need something that will manage what is on the "test" site vs. what is on the "live" site and user management, user permissions
code branches and built in cvs features
testing, approving code
again, code branches + testing site. as for code approval... you could just have people send in diffs for approval with only a few people with commit access to the CVS repo. also, bugzilla seems to be quite the nice fit for testing.
database change tracking
ok.. thats the kicker.. i have no idea how to pull this off in cvs. but again, could be done via code sumissions as diffs into a acceptance queue.
[/quote] etc all with a nice web interface. CVS doens't do that.[/quote]
there is cvsweb for tracking, and various 3rd party tools that interface cvs and web.
There's going to be about 25-30 people working on it at the same time.
thats easily manageable with a few people with checkin rights and code submission queues.
If you can come up with a PHP/MySQL-based system, that would be great!! ^_^
i dont see php/mysql as the end all be all of tools. IMO, cvs + submission queues seem to be quite a well fit to the problem.
this seems to be turning into a discussion that would be more suited to a chat then message board, so if you want, catch me on AIM, or we can arrange to meet up on irc somewhere.