August Carto Rebase

[jjmata]

Every month we should:

• [x] Fast-forward the master branch to pick up latest changes
• [x] Read NEWS.md in all relevant repos (here and here and here and here as well ... probably more) and adjust as necessary
• [x] Pick up any necessary changes to config files (app_config.yml and here and here as well)
• [x] Check /diagnosis and fix any regressions
• [ ] Peek at sverhoeven's repo for any lessons learned
• [x] Rebase the tileo branch
• [x] Rebase any other bits that we are working on but have not made the tileo branch yet (tileo-devops tends to have stuff "in progress" that hasn't been merged to tileo yet)
• [x] Rebase tileo-develop for new/WIP feature work
• [x] Promote "the build" to tileo-beta.co
• [x] Promote "the build" to tileo.co

May-specific tasks (carry-over!):

• [x] Make sure infowindows work in *.tileo.co
• [x] Pick up dataservices configuration example, see here
• [x] Add the crankshaft extension to the template_postgis database as per this suggestion
• [ ] Fix/upload NPM package to use for uploading data to tileo.co instead of carto.com, see here
• [ ] (optional) https://github.com/sverhoeven/docker-cartodb/commit/bbf2c543256ca4ef0f84099b9a680ded6108e756

June-specific tasks (carry-over!):

• [ ] (optional) Check to see if all DO changes landed (see issues 11663 and 12682, plus https://github.com/CartoDB/cartodb/milestone/135)
• [x] Re-brand email templates & Org pages

[jjmata]

Interesting items from June review of NEWS.md:

• [x] create_dev_user semantics: https://github.com/CartoDB/cartodb/pull/12187
• [ ] Org notifications: https://github.com/CartoDB/cartodb/issues/11850 (could be used for mobile app alarms)
• [ ] 'SQL function' analysis: https://github.com/CartoDB/cartodb/issues/12018
• [ ] Multiple file upload: https://github.com/CartoDB/cartodb/issues/11952
• [ ] Layers upgrade message: https://github.com/CartoDB/cartodb/issues/12167
• [ ] Pluggable frontends: https://github.com/CartoDB/cartodb/issues/11022

[jjmata]

Monthly might be too aggressive, we shall see. Maybe quarterly is a better cadence, or "when something of interest lands" could work too ... ;-) Thoughts @apercas and @MariaCheca?

[jjmata]

For instance, we could start "cherry-picking" interesting features and delaying the big rebase to every 3 months or so when something big happens like "new Mapnik" was, right?

Look at this one as a good cherry pick candidate:

• https://github.com/CartoDB/cartodb/issues/12421

[jjmata]

Tried to close this yesterday, but the rebase breaks widgets. Working with @apercas today to get a new cartodb.js branch that completes this work.

[jjmata]

Infowindows now work everywhere, @ivanprado!

(stupidest one-line configuration fix ever ... just needed the SSL port number explicitly stated in the config file)

[ivanprado]

¡¡¡Nice!!! :-D

[jjmata]

This was done a few weeks back. Closing (and creating the new one for after Fruit Attraction ...)