Skip to content
CARTO Spatial Analysis extension for PostgreSQL
Branch: develop
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github adds pep8 check item Oct 6, 2016
release Release 0.8.2 Feb 7, 2019
.brackets.json recommit from postgresql repo Aug 9, 2016
.gitignore Ignore idea based configurations Jun 9, 2016
.travis.yml Update CONTRIBUTING with information about PG function labels Nov 27, 2017
LICENSE Add licencse Feb 15, 2016
Makefile Remove reference to clean-environments #60 Jun 14, 2016 Makefile: Add support for PARALLEL categories Nov 27, 2017 News style: Release 0.8.2 Feb 8, 2019 Update RELEASE process Nov 27, 2017
carto-package.json PostGIS uses 4 numbers Aug 17, 2018 PG 11 Feb 7, 2019 Do not check code is updated when not needed Aug 11, 2016

Crankshaft Build Status

CARTO Spatial Analysis extension for PostgreSQL.

Code organization

  • doc/ documentation
  • src/ source code
  • pg/ contains the PostgreSQL extension source code
  • py/ Python module source code
  • release reseleased versions


  • PostgreSQL
  • plpythonu and postgis extensions
  • python-scipy system package (see src/py/

Development Process

We distinguish two roles:

  • developers will implement new functionality and bugfixes into the codebase.
  • A release manager will handle the release process.

We use the branch develop as the main integration branch for development. The master is reserved to handle releases.

The process is as follows:

  1. Create a new topic branch from develop for any new feature or bugfix and commit their changes to it:
git fetch && git checkout -b my-cool-feature origin/develop
  1. Code, commit, push, repeat.
  2. Write some tests for your feature or bugfix.
  3. Update the doc.
  4. Create a pull request and mention relevant people for a peer review.
  5. Address the comments and improvements you get from the peer review.
  6. Mention @CartoDB/dataservices in the PR to get it merged into develop.

In order for a pull request to be accepted, the following criteria should be met:

  • The peer review should pass and no major issue should be left unaddressed.
  • CI tests must pass (travis will take care of that).

Development Guidelines

For a detailed description of the development process please see the guide.


The tests (both for SQL and Python) are executed by running, from the top directory:

sudo make install
make test


The release process is described in the guide and is the responsibility of the designated release manager.

You can’t perform that action at this time.