1 / 9

Why Bitkeeper

Why Bitkeeper. Elliott Wolin GLUEX Collaboration meeting 20-22 May 2004. SCM History. Two revolutions within the past 27 years 1st revolution focus switched from files  repository 2 nd revolution focus switched from repository  workflow and release lifecycles

marshall-porter
Download Presentation

Why Bitkeeper

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Why Bitkeeper Elliott Wolin GLUEX Collaboration meeting 20-22 May 2004

  2. SCM History • Two revolutions within the past 27 years • 1st revolution focus switched from • files  repository • 2nd revolution focus switched from • repository  workflow and release lifecycles • Note that Bitkeeper is a superset of CVS

  3. Why Move to 3rd Generation SCM Save Time and Manpower BK Used by Linux kernel, MySQL, etc. Free BKL (not GPL!) license acceptable to us.

  4. What is New in 3rd Generation • Multiple, hierarchical repository structure • Reparenting • Changesets • Many other improvements, utilities, etc. • Full support for “gatekeeper” model • BK is a full-featured commercial product • Very active development (unlike CVS)

  5. Who Will Be Affected • Group 1 – casual programmers • Few thousand lines of code or less • Impact: -0.5 to+2 • Group 2 – major developers, integrators • Tens of thousands of lines of code or more • Impact: +2 to +7 • Group 3 – managers, librarians, integrators • Impact: +10!

  6. For CVS Users

  7. Summary • In midst of 2nd revolution in SCM software • 3rd generation has real advantages for us • Hierarchical repository structure, reparenting, changesets, supports gatekeeper model, etc. • Active product development • Minor change, minor benefit for most people • Major benefits for integrators, librarians, package managers, etc. • We should start using BK on new projects now!

  8. References • My earlier technical talk on BK: www.jlab.org/Hall-D/presentations/Bitkeeper_for_Hall_D.ppt • Bitkeeper web site: www.bitmover.com • SUN note on SCM strategies: www.jlab.org/Hall-D/software/teamware.ps • List of current SCM software: www.dmoz.org/Computers/Software/Configuration_Management/Tools • BK screenshots: www.bitkeeper.com/Products.BK_Pro.Screen.html • CVS to BK: www.bitkeeper.com/cvs2bk.html • Repository strategy from BK: www.bitkeeper.com/Products.BK_Pro.Feature_.html

  9. Additional Notes • I’ve used: patchy, sccs, rcs, cms, cmz, cvs, CM, Teamware, bitkeeper • Analogy: Fortran  OO programming

More Related