{"thread":{"id":"16831","subject":"Perl 5 now uses Git for version control","startedAt":"2008-12-22T11:32:27Z","lastAt":"2008-12-22T23:24:50Z","messageCount":2,"participants":["demerphq","Daniel Barkalow"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"98543","messageId":"9b18b3110812220332u4cae3a89rf957cbf96af530bf@mail.gmail.com","threadId":"16831","inReplyTo":"a92222c80812212356p766345aaj5f4dc31ebba616aa@mail.gmail.com","subject":"Perl 5 now uses Git for version control","fromName":"demerphq","fromEmail":"demerphq@gmail.com","sentAt":"2008-12-22T11:32:27Z","receivedAt":"2008-12-22T11:32:27Z","isPatch":false,"sender":{"key":"demerphq@gmail.com","avatar":null},"body":"HOLLAND, Michigan - The Perl Foundation has migrated Perl 5 to the Git\nversion control system, making it easier than ever for Perl's development\nteam to continue to improve the language that powers many websites.\n\nMoving from Perforce to git provides a number of benefits to the Perl\ncommunity:\n\n- With a public repository and Git's extensive support for distributed\nand offline work, working on Perl 5's source becomes easier for everyone\ninvolved.\n\n- Because Git is open source, all developers now have equal access to\nthe tools required to work on Perl's codebase.\n\n- Core committers have less administrative work to do when integrating\ncontributed changes.\n\n- Developers outside the core team can more easily work on experimental\nchanges to Perl before proposing them for inclusion in the next release.\n\n- A vast array of improved repository and change analysis tools are now\navailable to Perl's developers.\n\n- The new Git repository includes every version of Perl 5 ever released,\nas well as every revision made during development.\n\nInterested developers can get a copy of the Perl 5 Git repository at\nat http://perl5.git.perl.org/perl.git\n\nIn true open source style, Sam Vilain converted Perl's history from\nPerforce to Git. He did the work both in his spare time and in time\ndonated by his employer, Catalyst IT. He spent more than a year building\ncustom tools to transform 21 years of Perl history into the first\never unified repository of every single change to Perl. In addition\nto changes from Perforce, Sam patched together a comprehensive view\nof Perl's history incorporating publicly available snapshot releases,\nchanges from historical mailing list archives and patch sets recovered\nfrom the hard drives of previous Perl release engineers.\n\nPerl 5 is used by businesses around the world including the BBC,\nAmazon.com, LiveJournal, Ticketmaster, Craigslist and IMDb. Larry Wall\ncreated Perl in 1987 while working as a systems administrator for NASA.\n\nLarry released Perl 1.000 on December 18th 1987. Over the past 21 years,\nPerl has grown into a high-level, general-purpose, dynamic programming\nlanguage and is widely used for Web development, Systems Administration,\nGenomics and in many other disciplines. The most recent major version\nof Perl 5 (5.10.0) was released one year ago.\n\nGit is an open source version control system designed to handle very\nlarge projects with speed and efficiency. Created by Linus Torvalds,\nthe inventor of Linux to handle the vast number of contributions to\nthe Linux Kernel, Git is highly flexible and extensible. Perl's motto,\n\"There's More Than One Way To Do It!\" perfectly matches the Git workflow.\n\nNicholas Clark, the manager for Perl 5.8.9 which was released this week,\nsaid \"I'm looking forward to Git giving me the ability to work either\nonline or offline. Perforce is great when I have a network connection,\nbut until now those times when I've been trying to develop on trains\nor planes, at stations or airports, I'm back in the 'dark ages' before\nversion control. Git solves this problem and more\".\n\nThe hardware behind this and the systems administration time to maintain\nit is donated by Booking.com. Booking.com has also recently donated\n$50,000 to The Perl Foundation, to aid in the further development and\nmaintenance of the Perl programming language in general, and Perl 5.10\nin particular.\n\nPerl originally used the Revision Control System (RCS) until March\n1997 when it switched to the Perforce Software Configuration Management\nSystem. The Perforce repository was graciously hosted and maintained,\nfree of charge, by ActiveState. Perforce provided the core developers\nwith powerful tools, but these tools were not available to users outside\nthe core team. The switch to Git removes this barrier.\n\nAbout The Perl Foundation (http://www.perlfoundation.org/) | The Perl\nFoundation is dedicated to the advancement of the Perl programming\nlanguage through open discussion, collaboration, design, and code. The\nPerl Foundation coordinates the efforts of numerous grass-roots Perl-based\ngroups, including: International Yet Another Perl Conferences (YAPC's),\nCarries the legal responsibility for Perl 5 and Perl 6 and the Artistic\nand Artistic 2.0 licenses, perl.org, Perl Mongers, and PerlMonks.\n\nAbout Booking.com (http://www.booking.com/) | Booking.com is part of\nPriceline.com (Nasdaq: PCLN). Its website attracts an average of 30\nmillion unique visitors each month. Booking.com works with more than\n57,000 affiliated hotels in 15,000 destinations around the world. Its\nservices are available in 21 languages. Booking.com currently has 24\noffices in Amsterdam, Athens, Barcelona, Berlin, Cambridge, Cape Town,\nDubai, Dublin, London, Loulé (Portugal), Lyon, Madrid, Moscow, Munich,\nNew York, Orlando, Paris, Rome, San Francisco, Sydney, Singapore,\nStockholm, Vienna and Warsaw.\n\nAbout Catalyst IT (NZ) Ltd (http://www.catalyst.net.nz/) | Catalyst IT\nis New Zealand's premiere Open Source development house. Catalyst looks\nafter the development requirements for the NZ Electoral Enrolment Centre,\nmanage the .NZ registry, the largest NZ newspaper's online presence,\nthe NZ TAB and many other exciting projects, and are organising the 2010\nAustralasian Linux Conference to be held in Wellington, New Zealand.\n\n\nhttp://use.perl.org/articles/08/12/22/0830205.shtml\n\n-- \nperl -Mre=debug -e \"/just|another|perl|hacker/\"\n"},{"id":"98570","messageId":"alpine.LNX.1.00.0812221608410.19665@iabervon.org","threadId":"16831","inReplyTo":"9b18b3110812220332u4cae3a89rf957cbf96af530bf@mail.gmail.com","subject":"Re: Perl 5 now uses Git for version control","fromName":"Daniel Barkalow","fromEmail":"barkalow@iabervon.org","sentAt":"2008-12-22T23:24:50Z","receivedAt":"2008-12-22T23:24:50Z","isPatch":false,"sender":{"key":"barkalow@iabervon.org","avatar":"https://avatars.githubusercontent.com/u/55364219?v=4"},"body":"On Mon, 22 Dec 2008, demerphq wrote:\n\n> In true open source style, Sam Vilain converted Perl's history from\n> Perforce to Git. He did the work both in his spare time and in time\n> donated by his employer, Catalyst IT. He spent more than a year building\n> custom tools to transform 21 years of Perl history into the first\n> ever unified repository of every single change to Perl. In addition\n> to changes from Perforce, Sam patched together a comprehensive view\n> of Perl's history incorporating publicly available snapshot releases,\n> changes from historical mailing list archives and patch sets recovered\n> from the hard drives of previous Perl release engineers.\n\nAt some point, some of the custom tools were visible to the public \n(although not widely announced), and they include such things as an \nelaborate algorithm to figure out what a perforce depot's contents is \nsupposed to mean in a number of weird cases. Are these going to be \nofficially released, or are they considered to have served their purpose \nand be no longer interesting?\n\nI'd be interested to see the final version, and I think it would be useful \nto anyone working on interoperation between perforce and git (even though \nthe actual code needs a copy of the perforce database and is not \nincremental).\n\n\t-Daniel\n*This .sig left intentionally blank*\n"}]}