Friday, March 27, 2009

News on PostgreSQL source-code management

About a year ago, we started a Git hosting and mirroring service for the PostgreSQL project. Judging from feedback, comments, and the number of people who post obviously git generated patches, this service was widely welcome. Within the next few days, we will be moving this service onto a new backend infrastructure, which will allow even more people and projects to use this service, with decreased administration overhead and better performance. You will likely see a separate announcement when this is all set up and ready to use.

In the meantime, the committers of PostgreSQL have voted to stick with CVS as the master source code repository. This means that for the time frame of the development of version 8.4 + 1, there will be no project-wide move to another source-code management system for the master storage.

How does this make sense?

For those 6,769,383,230 of you out there who are not PostgreSQL committers, you can use any source-code management system you want, using various CVS conversion services. It's already possible and widely practiced to participate in PostgreSQL development day to day without using CVS at all. The PostgreSQL project system administrators are now putting more effort and resources into making sure that if Git is your choice, this choice is robustly supported. But there are other choices if Git is not your thing. (But read between the lines: More PostgreSQL hackers will be familiar with Git and CVS than any other system.) At the same time, the 15 committers will be able to continue to use the tool they are most comfortable with. Consider it rebasing in a weird way. So this way, it can be hoped that everyone wins, as they say.


  1. Where did you come up with the 6,769,383,230 number?

  2. There are a number of purported live world population counters out there, e.g., I can't remember which one I used, but it was the number I got minus 15. :-)