grunt release removes release dir

[XhmikosR]

Is the release dir obsolete now? If so someone should remove it from the repository.

@nschonni

[nschonni]

I think it is still probably needed for the non-NPM runners to be able to get the built files

[XhmikosR]

Actually, I end up with /build and release/build

[XhmikosR]

I would suggest just getting rid of either build or release and have one common destination folder.

[XhmikosR]

BTW, this must be related to npm install -g failing.

C:\Users\xmr\Desktop\csslint>npm install -g
npm http GET https://registry.npmjs.org/parserlib
npm http 304 https://registry.npmjs.org/parserlib
npm ERR! Error: ENOENT, chmod 'C:\Users\xmr\AppData\Roaming\npm\node_modules\csslint\cli.js'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR!     <http://github.com/npm/npm/issues>

npm ERR! System Windows_NT 6.1.7601
npm ERR! command "C:\\Program Files\\nodejs\\\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "-g"
npm ERR! cwd C:\Users\xmr\Desktop\csslint
npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3
npm ERR! path C:\Users\xmr\AppData\Roaming\npm\node_modules\csslint\cli.js
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR!     C:\Users\xmr\Desktop\csslint\npm-debug.log
npm ERR! not ok code 0

We really need a dist or build or whatever dir in root and just get rid of the release dir...