mirror of
https://github.com/CartoDB/crankshaft.git
synced 2024-11-01 10:20:48 +08:00
13d8c9acc3
Bumps [scipy](https://github.com/scipy/scipy) from 0.14.0 to 1.10.0. - [Release notes](https://github.com/scipy/scipy/releases) - [Commits](https://github.com/scipy/scipy/compare/v0.14.0...v1.10.0) --- updated-dependencies: - dependency-name: scipy dependency-type: direct:production ... Signed-off-by: dependabot[bot] <support@github.com> |
||
---|---|---|
.github | ||
doc | ||
release | ||
src | ||
.gitignore | ||
.travis.yml | ||
carto-package.json | ||
check-compatibility.sh | ||
check-up-to-date-with-master.sh | ||
CONTRIBUTING.md | ||
LICENSE | ||
Makefile | ||
Makefile.global | ||
NEWS.md | ||
README.md | ||
RELEASE.md |
Crankshaft
CARTO Spatial Analysis extension for PostgreSQL.
Code organization
doc/
documentationsrc/
source code
pg/
contains the PostgreSQL extension source codepy/
Python module source code
release
released versions
Requirements
- PostgreSQL
- plpythonu (for PG12+, plpython3u) and postgis extensions
- python-scipy system package (see src/py/README.md)
Development 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:
- 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
- Code, commit, push, repeat.
- Write some tests for your feature or bugfix.
- Update the NEWS.md doc.
- Create a pull request and mention relevant people for a peer review.
- Address the comments and improvements you get from the peer review.
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 CONTRIBUTING.md guide.
Testing
The tests (both for SQL and Python) are executed by running, from the top directory:
sudo make install
make test
Release
The release process is described in the RELEASE.md guide and is the responsibility of the designated release manager.