With the closing of Google Code, I will be moving my projects, a priori to BitBucket.
The new URL is https://bitbucket.org/egrange/dwscript
If you have Issues in the Google Code Issue Tracker that matter to you, please copy-paste them to the BitBucket Issue Tracker.
There are few enough active tickets, and the “automatic” import is too convoluted (and would lose many things) to make a “manual import” of the issues preferable, plus if you report it yourself, you’ll be able to report it under your account, and thus be notified of progress.
As for the reason why it’s on BitBucket, well, it’s a matter of features missing on GitHub (like binary downloads) and of personal Web UI preferences.
The source is also present on GitHub at https://github.com/EricGrange/DWScript, but that will be a secondary repository, not always up to date, and mostly so that myopic open-source analysis and studies will account for my code towards the Pascal & Delphi scores 🙂
9 thoughts on “DWScript moving to BitBucket”
For all of us that still have to move the repo – can you post the steps needed to move it to the BitBucket?
I know that Google Code implements some helper for transferring everything to GitHub but there’s no such helper for BitBucket.
As far as I can tell BitBucket doesn’t support SVN (GitHub does), so what are SVN users supposed to do?
@SpeedFreak use TortoiseGit, it makes git quite palatable.
@gabr the Google Code export to github failed for me (with an unspecified error 25% of the way). To summarize, you do a clone with git svn, then you can push the result to the git repository at BitBucket.
I will try to document the next project I migrate that way, with TortoiseGit screenshots.
Eric, I’m well aware that you you can access BitBucket with a git client, but that doesn’t help the existing client systems that are using svn.
I have no problem using a git client on my own systems, as I already do, but I think I will have a difficult time explaining to my corporate customers that they need to start using git on their build systems because of “Erics personal Web UI preferences”. Anyway, I don’t expect any changes, but I just wanted to remind you that your personal choices wrt. DWS have consequences beyond your sandbox.
Eric, you may want to try again – Google Code’s Github exporter tool fails sometimes due to the enormous workload.
The good thing about the exporter is that it will export its issues and wikis as well, IIRC.
I love Bitbucket but I moved my small projects to Github because of the convenience.
Thanks for upgrading to git. It’ll make contributions much easier (I think I have some small fixes floating around only in my repository).
@SpeedFreak well, at the moment I replicate the repo in two distinct SVN repository with non-open-source extras, but this comes as a service (part of a commercial agreement). You are free to maintain your own copy in an SVN repository for your customers 🙂
@Leonardo on a smaller project I found the issues were exported, but not their assignments, notification or classification (which is normal, different user accounts), and since there are not that many issues, it’ll be a good opportunity for cleaning up
FWIW, “a priori” doesn’t mean what you think it means. It’s a phrase used in philosophical and mathematical reasoning: http://en.wikipedia.org/wiki/A_priori_and_a_posteriori
@David, it depends in which language and context you use it.
The Latin, and vernacular French meaning, for instance, is exactly what Eric intended. As per your wiki entry: “The phrases “a priori” and “a posteriori” are Latin for “from what comes before” and “from what comes later” “.
Until Eric has done the move, he presupposes it will be in BitBucket. We will be able to see what he chose “a posteriori”.
Comments are closed.