Skip to content

Commit

Permalink
Merge branch 'release/3.15.9'
Browse files Browse the repository at this point in the history
  • Loading branch information
xavijam committed Feb 1, 2016
2 parents 1fddb38 + a722872 commit c9702bb
Show file tree
Hide file tree
Showing 64 changed files with 3,137 additions and 2,612 deletions.
703 changes: 0 additions & 703 deletions NEWS

This file was deleted.

827 changes: 827 additions & 0 deletions NEWS.md

Large diffs are not rendered by default.

3 changes: 0 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,6 @@
CartoDB.js (v3.15)
===========

[![Build Status](http://clinker.cartodb.net/desktop/plugin/public/status/CartoDB-js-develop-testing)]
(http://clinker.cartodb.net/jenkins/job/CartoDB-js-develop-testing)

This library allows to embed visualizations created with CartoDB in your map or website in a simple way.


Expand Down
16 changes: 8 additions & 8 deletions RELEASING.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
- Create a new branch to prepare the release:

```
git flow release start 3.15.4
git flow release start 3.15.9
```

- Build CartoDB.js files, choosing the new version:
Expand All @@ -25,7 +25,7 @@ grunt release
- Update the NEWS file and commit the changes. Take into account that new CartoDB.js version will be replaced in ```API.md```, ```RELEASING.md```, ```README.md```, ```package.json```, ```cartodb.js``` and ```examples``` files.

```
git commit -am "Files changed for version 3.15.4"
git commit -am "Files changed for version 3.15.9"
```

- Release it.
Expand All @@ -36,17 +36,17 @@ grunt publish

- Check if those files have been updated in the CDN:
```
http://libs.cartocdn.com.s3.amazonaws.com/cartodb.js/v3/3.15.4/cartodb.js
http://libs.cartocdn.com/cartodb.js/v3/3.15.4/cartodb.js
http://libs.cartocdn.com.s3.amazonaws.com/cartodb.js/v3/3.13/cartodb.js
http://libs.cartocdn.com/cartodb.js/v3/3.13/cartodb.js
http://libs.cartocdn.com.s3.amazonaws.com/cartodb.js/v3/3.15.9/cartodb.js
http://libs.cartocdn.com/cartodb.js/v3/3.15.9/cartodb.js
http://libs.cartocdn.com.s3.amazonaws.com/cartodb.js/v3/3.15/cartodb.js
http://libs.cartocdn.com/cartodb.js/v3/3.15/cartodb.js
```
- Sometimes It takes more than 10 minutes, if it is not updated, execute ```grunt invalidate```.

- And to finish: close the release and push it.

```
git flow release finish 3.15.4
git flow release finish 3.15.9
git push --all
git push --tags
```
Expand Down Expand Up @@ -75,7 +75,7 @@ grunt
grunt publish
```

For example, if we are in 3.15.4 and we want to go back to 3.13.4
For example, if we are in 3.15.9 and we want to go back to 3.13.4

```
git checkout 3.13.4
Expand Down
2 changes: 1 addition & 1 deletion bower.json
Original file line number Diff line number Diff line change
Expand Up @@ -4,7 +4,7 @@
"cartodb.js",
"themes/css/cartodb.css"
],
"version": "3.15.1",
"version": "3.15.9",
"homepage": "https://github.com/CartoDB/cartodb.js",
"authors": [
"CartoDB <[email protected]>"
Expand Down
25 changes: 14 additions & 11 deletions bower.sh
Original file line number Diff line number Diff line change
Expand Up @@ -10,9 +10,8 @@ ORG=CartoDB
REPO=cartodb.js-bower

# prepare repo folder
if [ -d $REPO ]
then
rm -rf $REPO
if [ -d $REPO ]; then
rm -rf $REPO
fi

# clone repo
Expand All @@ -32,17 +31,21 @@ cp -R bower.json $REPO/bower.json

cp -R LICENSE $REPO/LICENSE.md

# commit and tag repo
echo "-- Committing and tagging $REPO"
cd $REPO
git add -A
CARTODBJS_VER=$(git diff bower.json | grep version | cut -d':' -f2 | cut -d'"' -f2 | sort -g -r | head -1) && if [ $(echo $CARTODBJS_VER | wc -m | tr -d ' ') = '1' ]; then echo 'VERSION DID NOT CHANGE'; else git tag -a $CARTODBJS_VER -m "Version $CARTODBJS_VER"; fi
git tag -a $CARTODBJS_VER -m "Version $CARTODBJS_VER"
git commit -m "v$CARTODBJS_VER"

echo "-- Pushing $REPO"
git push -fq origin master
git push -fq origin --tags
NEW_VERSION=$(git diff origin/master bower.json | grep version | cut -d':' -f2 | cut -d'"' -f2 | sort -g -r | head -1)
if [ -z "$NEW_VERSION" ]; then
echo 'VERSION DID NOT CHANGE'
else
echo "-- Tagging $NEW_VERSION"
git tag -a $NEW_VERSION -m "Version $NEW_VERSION";
git commit -m "v$NEW_VERSION"

echo "-- Pushing $REPO"
git push -fq origin master
git push -fq origin --tags
fi

cd ..

Expand Down
Loading

0 comments on commit c9702bb

Please sign in to comment.