Skip to content
No description, website, or topics provided.
PLpgSQL Python Other
Branch: develop
Clone or download
Latest commit 6a063ca Apr 12, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Include instructions to load fixtures Apr 17, 2018
doc Merge pull request #317 from CartoDB/316-docs_schema Nov 7, 2017
release Remove new fields not used to simplify deploy process Apr 19, 2018
.gitignore first-pass automatic testing May 12, 2016
.travis.yml Refactor OBS_GetAvailableTimespans Apr 11, 2018
LICENSE Initial commit with what I think we need Apr 6, 2016
Makefile remove plpython and python code for now. also removed mistaken instal… Jan 25, 2017 Initial commit with what I think we need Apr 6, 2016 Updated Jul 3, 2018 Fix relative links in markdown Apr 13, 2016

Observatory extension

CartoDB extension that implements the row-level functions needed by the Observatory Service.

Code organization

├── doc     # documentation
├── release # released versions
└── src     # source code
    └── pg
        ├── sql
        └── test
            ├── expected
            ├── fixtures
            └── sql

Development workflow

We distinguish two roles regarding the development cycle:

  • developers will implement new functionality and bugfixes into the codebase and will request for new releases of the extension.
  • A release manager will attend these requests and will handle the release process. The release process is sequential: no concurrent releases will ever be in the works.

We use the default develop branch as the basis for development. The master branch is used to merge and tag releases to be deployed in production.

Developers shall create a new topic branch from develop for any new feature or bugfix and commit their changes to it and eventually merge back into the develop branch. When a new release is required a Pull Request will be open against the develop branch.

The develop pull requests will be handled by the release manage, who will merge into master where new releases are prepared and tagged. The master branch is the sole responsibility of the release masters and developers must not commit or merge into it.

Development Guidelines

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

Any modification to the source code shall always be done in a topic branch created from the develop branch.

Tests, documentation and peer code reviews are required for all modifications.

The tests are executed by running this from the top directory:

sudo make install
make test


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

You can’t perform that action at this time.