Merge branch 'development' into flag--ext

.changelogrc

@@ -2,10 +2,10 @@
     "app_name": "",
     "logo": "",
     "intro": "",
-    "branch" : "master",
+    "branch" : "development",
     "repo_url": "https://github.com/Unitech/pm2",
-    "version_name" : "2.10.4",
-    "tag": "2.10.3",
+    "version_name" : "3.0.1",
+    "tag": "3.0.0",
     "file": "currentTagChangelog.md",
     "template": "changelogTemplate.md",
     "sections": [
@@ -19,7 +19,7 @@
         },
         {
             "title": "Features",
-            "grep": "^feat"
+            "grep": "^feature"
         },
         {
             "title": "Documentation",

.drone.yml

@@ -14,12 +14,12 @@ pipeline:
       - ./packager/publish_deb_rpm.sh
     secrets: ['packagecloud_token']
     when:
-      event: tag          
+      event: tag
   build_apk:
     group: build
     image: keymetrics/alpine-pm2-builder:latest
     environment:
       - AWS_REPO_BUCKET=alpine-apk.pm2.io
     secrets: ['apk_rsa_priv_key', 'apk_rsa_pub_key', 'aws_access_key_id', 'aws_secret_access_key']
     when:
-      event: tag          
+      event: tag

.editorconfig

@@ -10,22 +10,6 @@ insert_final_newline = true
 indent_style = space
 indent_size = 2
 
-# JavaScript
-[*.js]
-indent_style = space
-indent_size = 2
-
-# YAML
-[*.yml]
-indent_style = space
-indent_size = 3
-
-# JSON
-[*.json]
-indent_style = space
-indent_size = 2
-
-# SHELL
-[*.sh]
-indent_style = space
-indent_size = 2
+# Makefile
+[Makefile]
+indent_style = tab

.github/CONTRIBUTING.md

@@ -12,11 +12,11 @@ We 'd like to keep our master branch as clean as possible, please avoid PRs on m
 
 ## Fire an issue
 
-When you got an issue by using pm2, you will fire an issue on [github](https://github.com/Unitech/pm2). We'll be glad to help or to fix it but the more data you give the most fast it would be resolved. 
+When you got an issue by using pm2, you will fire an issue on [github](https://github.com/Unitech/pm2). We'll be glad to help or to fix it but the more data you give the most fast it would be resolved.
 Please try following these rules it will make the task easier for you and for us:
 
 #### 1. Search through issues if it hasn't been resolved yet
-#### 2. Make sure that you provide following informations: 
+#### 2. Make sure that you provide following informations:
   - pm2 version `pm2 --version`
   - nodejs version `node --version`
   - operating system
@@ -27,7 +27,7 @@ Please try following these rules it will make the task easier for you and for us
   - How may I reproduce this? (this isn't easy in some cases)
   - Are you using a cluster module? Are you trying to catch SIGTERM signals? With `code` if possible.
 
-#### 4. Think global 
+#### 4. Think global
 If your issue is too specific we might not be able to help and stackoverflow might be a better place to seak for an answer
 
 #### 5. Be clear and format issues with [markdown](http://daringfireball.net/projects/markdown/)
@@ -37,4 +37,4 @@ Note that we might understand english, german and french but english is prefered
 
 ```DEBUG=pm2:* PM2_DEBUG=true ./bin/pm2 --no-daemon start my-buggy-thing.js```
 
-If your issue is flagged as `need data` be sure that there won't be any upgrade unless we can have enough data to reproduce. 
+If your issue is flagged as `need data` be sure that there won't be any upgrade unless we can have enough data to reproduce.

.gitignore

@@ -17,3 +17,4 @@ package-lock.json
 currentTagChangelog.md
 joblog-X
 test/fixtures/path-check*.txt
+yarn.lock

.npmignore

@@ -1,7 +1,7 @@
 test
 apps
 doc
-pres
+/pres
 *.log
 *.pid
 examples

CONTRIBUTING.md

@@ -111,8 +111,8 @@ npm install git-changelog -g
 
 ### usage
 
-Edit .changelogrc  
-Change "version_name" to the next version to release (example 1.1.2).  
+Edit .changelogrc
+Change "version_name" to the next version to release (example 1.1.2).
 Change "tag" to the latest existing tag (example 1.1.1).
 
 Run the following command into pm2 directory