Subversion and bug tracking

  • 375 views
Uploaded on

Comparing some SVN and Bug Tracking Systems

Comparing some SVN and Bug Tracking Systems

More in: Business , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
375
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
17
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. SUBVERSION AND BUG TRACKING By. Amira Elsayed Ismail
  • 2. ROLES No Side Talks Please Rewards for Good Listener Punishment for Bad Listener
  • 3. AGENDA Version Control Bug Tracking
  • 4. VERSION CONTROL Version Control  A version control system is simply a system that catalogs your changes and keeps them in an orderly fashion which also allows others to collaborate on the same project  Allow you to track changes (who, when, how it affected your project)  It helps you to simply picking a backup at some point, restoring it
  • 5. VERSION CONTROL (CONT’D) Concurrent Versions System (CVS)  Also known as Concurrent Versioning System  Uses client server architecture –this means that a server stores a current version (or versions) of a particular project as well as saving its history  The client then connects to the server as means to “check out” a copy of the project  Can maintain different branches of a project  Different aspects or permutations of the same project may branch off from the source project and CVS will maintain all versions  A released version of the project forms one branch for bug fixes, while a different version that is currently being developed may contain new features and major changes and form a branch of the same project
  • 6. VERSION CONTROL (CONT’D) Subversion (SVN)  Is a version control system used to maintain the current and preceding versions of files (like source code, web pages, and documentation)  It is a direct upgrade of CVS and its most compatible successor  It is also an open source technology and has been widely used in multiple projects (Apache, Free Pascal, Google code)  Creates a set of tentative changes and makes them permanent– as true atomic  Subversion also allows users to rename, copy, move, and/or remove files; however, those files will retain their full revision history  Subversion also costs according to the change size and not the size of the data
  • 7. CVS SVN Maintains the current and precedingMaintain different branches of a project versions of files Commits as true atomic operations.Based on RCS files of versions controlEach file is an ordinary file containing some Uses parsable outputinfo So the tree of these files repeatsYou should not be worry about data loss The basis of SVN is a relational databaseWorks slowly Works faster than CVS Allows to "attach" to a file any number of allAllows to store of only files and nothing else possible named attributesThe storage (binary, Unicode) is not trivial Manipulates all the file typesand requires special informationAllows to rollback any commit in the SVN does not allow rollback of commitrepositoryNo Transaction Support Transaction Support
  • 8. VCSs DVCSs One repository is as good as any other, and thatThere is One True Source, All developers work merges from one repository to another are justfrom that source, and then ad their changes another form of communicationIf your project or organization wants centralized If your developers are expected to work all overcontrol the worldTakes a client server approach Takes a peer-to-peer approach Common operations (commits,…) are fast,The repository must be available every time you because there is no need to communicate with awant to commit your changes central serverOnly accessed by anyone having write access to Communication is only necessary when pushing orthe repository directories pulling changes to or from other peersConflicts may arise, if someone commit change in Allows users to work productively even when notthe same file and program can’t handle it connected to a network Participation in projects without requiring permissions from project authorities
  • 9. VERSION CONTROL (CONT’D) Version Control  Client-server model  Open source  Concurrent Versions System (CVS)  Subversion (SVN)  VisualSVN  Proprietary  RocketSVN  Autodesk Vault  Clear Case  Visual SourceSafe
  • 10. VERSION CONTROL (CONT’D) Version Control  Client-server model  Open source  Concurrent Versions System (CVS)  Subversion (SVN)  VisualSVN Can’t provide Demo  Proprietary  RocketSVN  Autodesk Vault  Clear Case  Visual SourceSafe No trail download
  • 11. VERSION CONTROL (CONT’D) Version Control  Distributed model  Open source  Bazaar  Git  Mercurial  Monotone  LibreSource  Proprietary  Bit Keeper
  • 12. DEMO
  • 13. BUG TRACKING Bug Tracking  Is a software application that is designed to help quality assurance and programmers keep track of reported software bugs in their work
  • 14. BUG TRACKING (CONT’D) Bug Tracking  Trac  Jira  Bugzilla  Bug Traker.NET  FogBugz  Assembla
  • 15. BUG TRACKING (CONT’D) Bug Tracking  Trac  Jira  Bugzilla Both are web based on an external  Bug Traker.NET server so we will not make Demo  FogBugz for them  Assembla
  • 16. Features Input interfaces• Workflow with triggers, timers, and conditions • Web• Dashboard with reporting widgets • Email• Customizable fields for each project • CLI• HTML, XML, RSS, PDF, Excel, Word, customizable • GUI charts • REST• Enterprise wiki • SOAP• Test planning integration • Mylyn• Customizable workflow • Visual Studio• Unicode support• SLA• Plugin API• Multiple ProjectNotification Revision control integration• Email • Git• RSS • Mercurial• XMPP • CVS • Subversion • Perforce • AccuRev • ClearCase
  • 17. Features Input interfaces•Integrated wiki •Web•Test planning integration •Mylyn•Customizable workflow•Unicode support•Custom Fields•Plugin APINotification Revision control integration•Email •Git•RSS •Mercurial •Bazaar •Monotone •Darcs •CVS •Subversion •Perforce •AccuRev
  • 18. Features Input interfaces• Integrated wiki • Web• Customizable workflow • Email• Unicode support • CLI• Custom Fields • REST• Plugin API • Mylyn • Visual Studio• Multiple Project • XMLNotification Revision control• Email integration• RSS • Mercurial • CVS • Subversion • Perforce
  • 19. Features Input interfaces• Integrated reports and charts • Web• Scheduled reports by mail • Email• Test planning integration • CLI• Customizable workflow • GUI• Unicode support • REST• Custom Fields • SOAP• Plugin API • Mylyn• Multiple ProjectNotification Revision control integration• Email • Git• RSS • Mercurial • Bazaar • CVS • Subversion • Perforce • AccuRev
  • 20. Features Input interfaces• Wiki syntax • Web• Email notification • Email• Linking to Subversion commits • CLI• Document manager • REST• Charts • Mylyn• Reports• Unicode Support• Custom Fields• Plugin API• Multiple ProjectNotification Revision control integration• Email • Git• RSS • Mercurial• Twitter • Subversion
  • 21. Features Input interfaces• Integrated charts and reports • Web• Customizable workflow • Email• Unicode support• Custom FieldsNotification Revision control integration• Email • Git • Mercurial • Darcs • Subversion
  • 22. DEMO