A few months later, we provided an updated version. The release was perfect to our great satisfaction. During preparation for one particularly release, the inexperienced tester, that is me, tested a version provided directly by the developer. However, team members were not using it consistently. Not using SVN consistently can result in version lossĪ few years ago, the team was still very inexperienced.The lesson is that adopting a good version control tool set will save time and energy. Later, after we adopted SVN, I came to realize that the diff command in SVN will provide the list simply in a few seconds. The process was tedious and error-prone, and often took me a few hours. As the team was very inexperienced and had not yet adopted SVN, I had to manually compare updates by Beyond Compare, export comparison results, and edit the difference list. I was responsible for providing the list. Years ago, one client was asking us for an add-delete-modify file list for every update we provided. Not using SVN can result in wasted labor.Other possible tools include GIT, CVS, etc. The version control tool sets we adopted are Apache, Subversion, Tortoise SVN Client, and Eclipse Subclipse Plug-in. I would like to share a few lessons about using version control tools. But for inexperienced teams, version control can still be challenging. Good version control enables teams to quickly locate and reconstruct versions, so as to swiftly assist delivery and trouble shooting. Version control is very import for software projects.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |