Re: Repository is moving
James Henstridge <[email protected]>
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Message-ID | <[email protected]> |
2009/4/26 Federico Di Gregorio <fog-NGVKUo/i/[email protected]>: > Hi *, > > I don't know exactly when but during the next few weeks initd.org will > undergo a complete upgrade. In the meantime I migrated psycopg2 to Git > and moved it to our firm server (this is probably a temporary solution, > the repo will move back to initd.org later). Why Git? > > 1. After we moved to bzr I got _less_ patches that when the repo > was hosted on SVN. I would guess that this had more to do with the disappearance of the web site and public bug tracker at around the same time. As there was no info on the web site about how to grab the latest source code, some people asked on the list. I'm sure there are others who didn't pursue things that far. Since the switch to Bazaar, we had a source code browser running off a mirror of the branch at bazaar.launchpad.net (using the open source Loggerhead web front end), but there was no way to get there from the placeholder project home page. If you want increased contribution, I think you'll need: * clear instructions on obtaining the source code. * clear instructions on how to submit changes * clear instructions on how to report bugs, preferably through a public bug tracker From my experience with other projects, you'll receive many patches from people without much version control experience, so it is important to have this no matter what system is in use. > 2. Some of the patches were even derived from local git > repositories. This'll give me an excuse to see how bzr-git has progressed ... > 3. The world is moving to Git. > 4. Our little firm completely switched to Git 6 months ago. > 5. Nobody except James provided a good reason to stay with bzr. > > I hope that this switch will allow more people to access psycopg2 source > code without having to wait for a release. (Yes, I know about the bug > tracker, I'll have a look at it ASAP). > > So, public read-only access to the repository: > > git://luna.dndg.it/public/psycopg2.git I checked this out and took a bit of a look at it. 1. the head revision contents appear to be the same as in Bazaar. 2. the revision DAG appears to have been converted correctly. The "git log" output makes it a bit difficult to compare, but "gitk" was understandable. Even the difficult merge between the 2_0_x and trunk branches I did a while back came through okay. 3. I was a bit surprised that the repository data was so much larger: 2.2MB for Bazaar and 7.5MB for Git. I thought Git did better than that in comparison to the Bazaar format we were using. Could there be something from another project hiding in there? Running "git gc" didn't seem to clear any space. 4. none of the tags or branches have been migrated from the old repo. This should be a simple matter of mapping from the old revision IDs that the tags/branches point at to the new ones. > > and gitweb access to the same repo: > > https://dndg.it/cgi-bin/gitweb.cgi?p=public/psycopg2.git This URL gives a certificate error in Firefox. It'd be good to fix that. http://www.startssl.com/ has free certificates for single domain sites and is in Mozilla's default set of certs, if that helps. James.