Go to file
2016-03-09 15:03:17 +01:00
doc Directory reorganization and sketch of new versioning procedure 2016-03-08 19:35:02 +01:00
src Use SciPy from system package python-scipy 2016-03-09 15:03:17 +01:00
CONTRIBUTING.md Update CONTRIBUTING.md 2016-02-23 17:23:33 +01:00
DEPLOYING.md Add a top-level Makefile 2016-02-19 11:57:13 +01:00
LICENSE Add licencse 2016-02-15 18:36:38 +01:00
Makefile Directory reorganization and sketch of new versioning procedure 2016-03-08 19:35:02 +01:00
README.md Use SciPy from system package python-scipy 2016-03-09 15:03:17 +01:00
TODO.md Add the cartodb extension as a dependency 2016-02-18 19:18:15 +01:00

crankshaft

CartoDB Spatial Analysis extension for PostgreSQL.

Code organization

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

Requirements

  • pip, virtualenv, PostgreSQL
  • python-scipy system package

Working Process

Development

Work in src/pg/sql, src/py/crankshaft; use topic branch.

Update local installation with sudo make install (this will update the 'dev' version of the extension in 'src/pg/')

Run the tests with PGUSER=postgres make test

Update extension in working database with

  • ALTER EXTENSION crankshaft VERSION TO 'current'; ALTER EXTENSION crankshaft VERSION TO 'dev';

Note: we keep the current development version install as 'dev' always; we update through the 'current' alias to allow changing the extension contents but not the version identifier. This will fail if the changes involve incompatible function changes such as a different return type; in that case the offending function (or the whole extension) should be dropped manually before the update.

If the extension has not previously been installed in a database we can:

Add tests...

  • CREATE EXTENSION crankshaft WITH VERSION 'dev';

Test

Commit, push, create PR, wait for CI tests, CR, ...

Release

To release current development version (working directory should be clean in dev branch)

(process to be gradually automated)

For backwards compatible changes (no return value, num of arguments, etc. changes...) new version number increasing either patch level (no new functionality) or minor level (new functionality) => 'X.Y.Z'. Update version in src/pg/crankshaft.control Copy release/crankshaft--current.sql to release/crankshaft--X.Y.Z.sql Prepare incremental downgrade, upgrade scripts....

Python: ...

Install the new release

make install-release

Test the new release

make test-release

Push the release

Wait for CI tests

Merge into master

Deploy: install extension and python to production hosts, update extension in databases (limited to team users, data observatory, ...)

Release manager role: ...

.sql release scripts commit tests: staging.... merge, tag, deploy...