Svn process

1,156 views

Published on

SVN Commit and process

Published in: Education, Technology, Business
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,156
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Svn process

  1. 1. SVN Process PRESENTED BY:
  2. 2. Sprint BacklogIdeal Scenario – For Agile Teams Trunk RC Product Product 1 2 Release Candidate Development phase US - 02 Development phase US - 01
  3. 3. Worst Case Scenario – For Agile Teams Change of Sprint Backlog Trunk plan - Not to release Product 2? RC Product Product 1 2 Release Candidate Development phase US - 02 Development phase US - 01
  4. 4. Sprint BacklogSVN Comment – For Agile Teams Trunk Change Of Plan SVN commit log format : RC [Users’ Initials] [Unique identifier*] [Type*][Friendly message] For Example : Release[#JIRA-0012] [Development][Swap inline implementation] [RAJ] Candidate *Unique identifier : User story / Defect number when not associated with any user story. *Type : Development / Defect Development phase US - 02 Development phase US - 01
  5. 5. Do’s : • Atomic commits •Each commit should reflect changes only for one user story or defect. • Follow the SVN commit log pattern •Refer slide 04 (SVN Comment) Don’t : • Never commit the changes of two different user story or defects at the same time.Do’s & Dont • Never commit with out the SVN log message. • Never commit with out the SVN log message as per the agreed format.

×