As we started a new phase in our project there was a discussion on whether to create a seprate SVN structure or continue using the old one for storing Project Artifacts. Finally we decided to create a seprate structure and kept both new svn and old one in a same directory folder with proper naming convention and contact information in comments feature of SVN.
Then we created a template of how we will keep our SVN folder structure.
For example whether to keep documents release specific or sprint specific.
Thanks to our scrum master we got certain valuable suggestions.
We uploaded that template as well in SVN folder. This template will help new team members know about the location of a specific document .
Are you following the same practice?
Subscribe to:
Post Comments (Atom)
Working with Compression on HDFS
Copy and uncompress file to HDFS without unziping the file on local filesystem If your file is in GB's then this command would cer...
-
Web Portals The IBM Cognos 8 Web portal is IBM Cognos Connection. IBM Cognos Connection replaces Upfront and the PowerPlay Table of Contents...
-
As part of setting up trigger-based scheduling, you must schedule an entry based on an occurrence. Trigger-based schedule is activated if th...
-
Few days back, I got an opportunity to prepare features list for Mobile reporting solution tool. We all know that days are not too far when...
No comments:
Post a Comment