Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Why Bitkeeper Elliott Wolin GLUEX Collaboration meeting 20-22 May 2004."— Presentation transcript:

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

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

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

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

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

6 For CVS Users cvs diff Display file differences bk diffs cvs update Update local repository from parent bk pull cvs add Add new file to local repository bk new cvs status Summary of local repository status bk status Commit local files as changeset  Repeat after add’l edit/ci cycles  bk commit cvs commit Push files back to parent repository bk push Unlock local files for editing bk edit Check in local files, incl. comment  Repeat edit/ci cycle  bk ci cvs checkout Clone repository locally (once) bk clone CVSDescriptionBK

7 Summary In midst of 2 nd revolution in SCM software In midst of 2 nd revolution in SCM software 3 rd generation has real advantages for us 3 rd generation has real advantages for us Hierarchical repository structure, reparenting, changesets, supports gatekeeper model, etc. Hierarchical repository structure, reparenting, changesets, supports gatekeeper model, etc. Active product development Active product development Minor change, minor benefit for most people Minor change, minor benefit for most people Major benefits for integrators, librarians, package managers, etc. Major benefits for integrators, librarians, package managers, etc. We should start using BK on new projects now! 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 My earlier technical talk on BK: www.jlab.org/Hall- D/presentations/Bitkeeper_for_Hall_D.ppt www.jlab.org/Hall- D/presentations/Bitkeeper_for_Hall_D.ppt www.jlab.org/Hall- D/presentations/Bitkeeper_for_Hall_D.ppt Bitkeeper web site: www.bitmover.com Bitkeeper web site: www.bitmover.com www.bitmover.com SUN note on SCM strategies: www.jlab.org/Hall- D/software/teamware.ps SUN note on SCM strategies: www.jlab.org/Hall- D/software/teamware.ps www.jlab.org/Hall- D/software/teamware.ps www.jlab.org/Hall- D/software/teamware.ps List of current SCM software: www.dmoz.org/Computers/Software/Configuration_Management/To ols List of current SCM software: www.dmoz.org/Computers/Software/Configuration_Management/To ols www.dmoz.org/Computers/Software/Configuration_Management/To ols www.dmoz.org/Computers/Software/Configuration_Management/To ols BK screenshots : www.bitkeeper.com/Products.BK_Pro.Screen.html BK screenshots : www.bitkeeper.com/Products.BK_Pro.Screen.html www.bitkeeper.com/Products.BK_Pro.Screen.html CVS to BK: www.bitkeeper.com/cvs2bk.html CVS to BK: www.bitkeeper.com/cvs2bk.html www.bitkeeper.com/cvs2bk.html Repository strategy from BK: www.bitkeeper.com/Products.BK_Pro.Feature_.html Repository strategy from BK: www.bitkeeper.com/Products.BK_Pro.Feature_.html www.bitkeeper.com/Products.BK_Pro.Feature_.html

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


Download ppt "Why Bitkeeper Elliott Wolin GLUEX Collaboration meeting 20-22 May 2004."

Similar presentations


Ads by Google