Skip to content
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

v0.9.0-rc* issues #330

Closed
4 tasks
indexzero opened this issue Dec 3, 2014 · 5 comments
Closed
4 tasks

v0.9.0-rc* issues #330

indexzero opened this issue Dec 3, 2014 · 5 comments

Comments

@indexzero
Copy link

Please post any issues you have with vows@0.9.0-rc1 here. It will not be installed as "latest" automatically yet. You will need to install it explicitly:

npm install -g vows@next
npm install vows@next

Or put the explicit version in your package.json:

{
  // other properties
  "devDependencies": {
    "vows": "0.9.0-rc1"
  }
}

the goal is to release 0.9.0 before the end of next week so please let us know if you have any problems with the release. There are some pretty big changes in there which are documented in the changelog. This is an important step to shipping 1.0.0 with some big wins so we appreciate your help!

Aside: known OSS modules to assure work
  • foreverjs/forever
  • foreverjs/forever-monitor
  • flatiron/winston
  • flatiron/nconf
@indexzero indexzero mentioned this issue Dec 3, 2014
@silkentrance
Copy link

Please see #331 and PR #332, thanks.

@indexzero
Copy link
Author

@silkentrance these have been fixed. Thanks for your contributions!

@indexzero indexzero changed the title v0.9.0-rc1 issues v0.9.0-rc* issues Jan 7, 2015
@markstos
Copy link

markstos commented Apr 6, 2016

Since all the issues reported with the 0.9.0 release have been fixed here and there have been further comments on it in over a eyar, could it be released now?

0.9.0 would fix a deprecation warning that's currently happening when using vows -v with 0.8.1 run with Node.js 4.4.2. The warning is:

  util.print is deprecated. Use console.log instead.

This issue has already been fixed in latest code on Github.

@evanp
Copy link
Contributor

evanp commented Apr 27, 2018

We ended up going in a different direction, so I'm closing this omnibus issue

@evanp evanp closed this as completed Apr 27, 2018
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

No branches or pull requests

4 participants