![]() However, the mirror proved too unreliableįor this purpose, and Andrew had to set up another mirror on Github using Transitioning build farm members to using the Git mirror in advance of the The Buildfarm developers, primarily Andrew Dunstan, worked on Developers had tested several back branches, and tweaked the conversion process until it was possible to produce a back-branch release which was identical to the one produced by CVS. The Buildfarm code had been patched, and the web team planned to set up aĬVS mirror of Git for the build farm members who could not run Git. It was also unclear whether it would be possible to recreate past releases from Git. The committers did not want to change this process. Using CVS, PostgreSQL contributors submitted their patches in context diff format to the pgsql-hackers mailing list and the CommitFest application. The second challenge was the code review process. The Buildfarm would need to be updated to use Git, which was aĬhallenge because not all of the operating systems represented in the buildįarm (such as UnixWare and AIX) had Git packages available. ![]() This network of donated servers and virtual machines doesĭaily or hourly CVS checkouts, builds PostgreSQL, and runs regression With a version of Git available for Windows, a major hurdle had been cleared, but several issues remained to be solved, most of them having to do with project infrastructure.įirst, the project has an automated regression testing infrastructureĬalled the PostgreSQL Buildfarm. It was time to switch to something, and a long discussion ensued at the developer meeting. By pgCon 2009, PostgreSQL was one of only a handful of major projects still using CVS. PgCon is the annual international PostgreSQL conference in Ottawa, Canada. By mid-2008, it was clear that a majority of PostgreSQL developers favored an eventual switch to Git. While one or two Subversion mirrors were created well before the Git mirror, and there was even a Bazaar mirror on Launchpad, none of these were at all popular. Synchronization with CVS was often undependable, with changes made in CVS failing to show up in Git. However, the mirror became a source of frustration for the developers who depended on it. But once the flames died out, many people started using the repository. This was done without obtaining community consensus, and caused some controversy. In 2008 a few members of the PostgreSQL web team decided to set up an "official", using FromCVS for conversion, and Gitweb with custom administration scripts for the web version. An increasing number of PostgreSQL contributors started using Git mirrors. This mirror was extremely popular and one Google Summer of Code student even did his project using the Git mirror instead of the CVS repository. In 2007, one of the git-cvsimport maintainers from New Zealand decided to set up a persistent and frequently updated Git mirror for the PostgreSQL CVS tree. ![]() In retrospect, this turned out to have been a good decision. The community verdict was to wait for one version control system to become the clear leader. And, of course, a large group of developers saw no reason to change at all.Īs with many projects which operate by rough consensus, where there is no consensus, there is no action. Into multiple camps based on the system they preferred, including Subversion, Arch, and Monotone. Those who wanted to migrate off of CVS split This discussion, and occasional flamewars, continued to crop up on the main Sufficiently mature at the time, or as offering enough advantages over CVS. In 2004, as Subversion was beginning to become popular, PostgreSQLĪbout switching away from CVS. A large web and development infrastructure existed around CVS, as well as a multi-step, multi-role release procedure. Twenty-one major releases and 154 minor releases were committed, branched, and packaged on CVS. Out of the ten-year-old university project. Generally considered the "birthday" of the open-source project, which came ![]() Inįact, the date the CVS server went live - Jis Mid-September 2010, the PostgreSQL Project was developed using CVS. Switching version control systems is a relatively straightforward processįor a young project, but not for an old one. Transition in their version control system may find useful lessons in how Other projects that are contemplating, or working on, a Making the switch happen took years and resulted in at least one The PostgreSQL Project finally switched from CVS to Git in September 2010,Īnd did its first release based on the new Git repository on October 5. ( agensgraph-git, postgresql-libs-9.5, postgresql-libs-9.4, postgresql-src-beta-libs, postgresql-libs-9.This article was contributed by Josh Berkus ![]() ( openssl-git, openssl-hardened, openssl-static, quictls-openssl) ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |