[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Noel L Yap
Mon, 18 Jun 2001 15:52:45 -0400
>1. Must be able to work with Patrol, JAVA, C, C++, SQL scripts
I don't know what Patrol is.
In practice, there's more renames and moves in Java than in other languages.
These ops are a pain in CVS.
I've seen no problems with other file types.
>2. Access to source controlled thru policies so developers only have access
>to the source they use
Use file permissioning for such things.
>3. Version control with ability to rollback to previous versions easily
>4. Must be able to work with UNIX and NT
>5. Must have a GUI interface
Yes (various frontends exist).
>6. Must have a command line interface
>7. Must have tracking and reporting capability to determine who has what
>and for how long
If you use the edit feature.
>8. Authentication by strong passwords or a digital certificate
>9. Must maintain an audit trail of source changes
>10. Must have encrypted communication between the client and the repository
>11. Source needs to be signed out to only one person
Only if all developers adhere to the rules. Typically there's no need to have
tools strictly enforce this. Look for discussions on reserved locks.
This communication is for informational purposes only. It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan Chase & Co., its
subsidiaries and affiliates.
- Re: CVS, Matthew Riechers, 2001/06/14
- CVS, Randall Weigers, 2001/06/18
- RE: CVS, Randall Weigers, 2001/06/18
- RE: CVS,
Noel L Yap <=