Skip to content

Add a changelog to our branch #13

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 5, 2017
Merged

Conversation

rafatower
Copy link

@Algunenano can you please take a quick look?

@rafatower rafatower requested a review from Algunenano December 5, 2017 12:08
@rafatower
Copy link
Author

cc'ing @pramsey for awareness.

I hope this is clear and simple enough FTM. I'm merging now to not defer things. I'll take care of any comments & suggestions later on.

@rafatower rafatower merged commit cfebe90 into REL_10_CARTO Dec 5, 2017
@rafatower rafatower deleted the REL_10_CARTO_changelog branch December 5, 2017 12:19
@Algunenano
Copy link

I'd add #10 too and leave a link in the Changelog to the PRs or issues for context.

@rafatower
Copy link
Author

I indeed added PR links for context: https://github.com/CartoDB/postgres/blob/REL_10_CARTO/CHANGELOG.carto.md#101carto-3

I'm experimenting with that 10.1+carto-3 but it shouldn't be painful at all to release a 10.1+carto-4 with the PR you mentioned (and deploy).

Thanks!

@Algunenano
Copy link

Looks good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants