From 4aed149bd67b51c53484a529a6dd3879b56544a7 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jes=C3=BAs=20Arroyo=20Torrens?= Date: Tue, 9 Mar 2021 09:19:31 +0100 Subject: [PATCH] Mark repo as deprecated --- README.md | 63 ++----------------------------------------------------- 1 file changed, 2 insertions(+), 61 deletions(-) diff --git a/README.md b/README.md index efe8b8b..06fd1fb 100644 --- a/README.md +++ b/README.md @@ -1,64 +1,5 @@ # Observatory extension -CartoDB extension that implements the row-level functions needed by the Observatory Service. +## :warning: Deprecated :warning: -## 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 [CONTRIBUTING.md](CONTRIBUTING.md) 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 -``` -## Release - -The release and deployment process is described in the -[RELEASE.md](RELEASE.md) guide and it is the responsibility of the designated -release manager. +This repository has been deprecated! No further maintenance or development will be done.