---------- Forwarded message ---------- From: [EMAIL PROTECTED] Date: Mon, 15 May 2006 19:23:43 -0000 Subject: Re: Managing large scale development To: "VistA" <[EMAIL PROTECTED]>
Since the primary intent of the VistA Community Meeting is to provide opportunities for the members of the community to interact, what is planned for the session is what you and other members of the community want in that session. Although I am not active in VistA development, let me hazard some guesses about the issues that need to be hashed out at the meeting: 1. Who should have the authority to make decisions about what makes it into the repository? How does the community decide who is a committer and who is not? 2. What procedures should be followed with respect to checking things into the repository? What criteria must be met before anything can be committed (design, code & test reviiew requirements, minimum test coverage, functional documentation, etc.)? What are the commit requirements (check-in comment requiring tracking number, reviewer';s name, etc.)? 3. How do we manage non-code aspects of version control (e.g,, using a code repository to track deltas in the database schema)? I am sure there are many more questions of this ilk that can be asked. -- Bhaskar ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Hardhats-members mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hardhats-members
