In defense of the original poster, a "shared" project is not uncommon. For example, Telelogic's CM Synergy allows for either private projects or shared ones. I've even worked on projects that used both simultaneously.
> > The sources are sources for database objects (stored procedures, > > triggers, ...) which are applied against a database, no user has it's > > own database, so it makes no sense to work in different areas, > > everbody will see everybody else's changes in the database anyway. The > > private sandbox isn't there. I've worked on an Oracle Financials customization project that sounds very similar. No single developer owned the database, but there were also two additional databases for integration testing and QA/UAT. The private project approach was the choice of the developers and works fine for this type of project, but the "shared" approach would have worked equally well. _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
