Browse files

Updates for version 0.6.0

  • Loading branch information...
1 parent 8918342 commit e7b6a97c3908b770366dc8a21100300492902686 @kunklejr kunklejr committed Sep 12, 2013
Showing with 55 additions and 18 deletions.
  1. +14 −0 CHANGELOG.md
  2. +37 −0 CONTRIBUTING.md
  3. +4 −18 package.json
View
14 CHANGELOG.md
@@ -167,3 +167,17 @@ Fix:
Fix:
- Add backticks to MySQL driver #114 (via @mstorgaard)
+
+## 0.6.0
+
+New Feature:
+ - Support varargs in runSql, all on mysql driver #119 (via @Gloridea)
+ - Load Environment Variables specified in config file #118 (via @codyhanson)
+ - Added CoffeeScript support for migrations #116 (via @DeniSix)
+
+Improvement:
+ - Added date type for sqlite3 #121 (via @mrcsparker)
+
+Fix:
+ - Fix postgres issue with camelCased column name definition #125 (via @virpool)
+
View
37 CONTRIBUTING.md
@@ -0,0 +1,37 @@
+Without pull requests from generous people like you, this project
+wouldn't be what it is today. You are planning to contribute aren't you?
+If so, here's a quick guide to creating a great pull request for
+this project:
+
+1. Fork the repo.
+
+2. Run the tests. Pull requests without tests are much less likely to be
+merged, and it's great to know you're starting with a clean slate: `npm test`.
+Be sure to check the README for setting up your test databases first.
+
+3. Add a test for your change. Refactoring and documentation changes
+require no new tests. If you are adding functionality or fixing a bug,
+please include a test.
+
+4. Make the test pass.
+
+5. Push to your fork and submit a pull request.
+
+At this point you're waiting on me. In a perfect world I'd commit to
+responding to your request in some short period of time. Unfortunately,
+I'm not able to do that. You'll most likely see me work off several pull
+requests in batches. I may suggest some changes or improvements or alternatives
+at that time. Please don't consider the feedback as a lack of
+appreciation for your time and effort. It most certainly is not.
+
+Some things that will increase the chance that your pull request is accepted,
+are:
+
+* Include good tests
+* Keep the changeset small
+* Stick to existing code conventions
+* Update the documentation, examples elsewhere, guides,
+ whatever is affected by your contribution
+
+See my [pull request etiquette](http://kunkle.org/blog/2013/07/10/pull-request-etiquette/)
+post for more contribution tips.
View
22 package.json
@@ -1,7 +1,7 @@
{
"name": "db-migrate",
"description": "Database migration framework for node.js",
- "author": "Jeff Kunkle <jeff.kunkle@nearinfinity.com>",
+ "author": "Jeff Kunkle",
"bin": "./bin/db-migrate",
"keywords": [
"database",
@@ -11,31 +11,17 @@
"sqlite",
"mysql"
],
- "version": "0.5.4",
+ "version": "0.6.0",
"engines": {
"node": ">=0.6.0"
},
- "maintainers": [
- {
- "name": "Jeff Kunkle",
- "email": "jeff.kunkle@nearinfinity.com"
- },
- {
- "name": "Joe Ferner",
- "email": "joe.ferner@nearinfinity.com"
- },
- {
- "name": "Aaron Probus",
- "email": "aaron.probus@nearinfinity.com"
- }
- ],
"bugs": {
- "url": "https://github.com/nearinfinity/node-db-migrate/issues"
+ "url": "https://github.com/kunklejr/node-db-migrate/issues"
},
"license": "MIT",
"repository": {
"type": "git",
- "url": "https://github.com/nearinfinity/node-db-migrate.git"
+ "url": "https://github.com/kunklejr/node-db-migrate.git"
},
"dependencies": {
"optimist": "~0.3.0",

0 comments on commit e7b6a97

Please sign in to comment.