darktable article lede image

tag: Download

Moving the git repo to github [done]

**Update: **the git repository officially resides in github now.

Today we are moving our git repo from sf.net to github, as it was agreed in the developer meeting that took place yesterday. This will happen today 22:00 – 23:00 CEST

What should I do now?

Depends on the role you play in the project.

  1. You have commit rights into current sf.net repository: please open an account in github if you don’t have any and make me know it. I will give you those permits there, but do not push there for now, your changed will be lost.
  2. You don’t have commit rights but regularly contribute back patches to darktable: please consider doing a fork of our repo in github and make a branch there for your patches. Later on make a pull request to let us know that we should pull from your branch.
  3. If you make some patches, but not in a regular way, you can also benefit of having your own fork … it will allow to publish your changes, access them from remote places, and have a backup place for your repo in case of disaster.
  4. You only track the repo. Wait until the switch is made and follow the instructions in this post.

What is going to happen just before the switch?


darktable 1.0.3 released

Pascal de Bruijn did some good work backporting some of the progress from git master to the 1.0 release. We packed that into a tarball, here it is:

https://sourceforge.net/projects/darktable/files/darktable/1.0/darktable-1.0.1.tar.gz/download

https://sourceforge.net/projects/darktable/files/darktable/1.0/darktable-1.0.3.tar.gz/download

(We had a problem packaging sources, so 1.0.3 is now on air. Please use it instead of 1.0.1)

As usual we have Ubuntu Packages are readily available on Pascal’s PPA, for Lucid, Natty, Oneiric and Precise:

https://launchpad.net/~pmjdebruijn/+archive/darktable-release

https://launchpad.net/~pmjdebruijn/+archive/darktable-release-plus

And these are the major changes: