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

1.0 #29

Open
7 of 8 tasks
mattlewis92 opened this issue Dec 6, 2016 · 7 comments
Open
7 of 8 tasks

1.0 #29

mattlewis92 opened this issue Dec 6, 2016 · 7 comments

Comments

@mattlewis92
Copy link
Contributor

mattlewis92 commented Dec 6, 2016

I think this module is relatively stable now, having a quick flick through the open issues it seems most of them are resolved by recently merged or outstanding PRs. There are a few more things I think we should do before putting a 1.0 label on the module

  • review and merge outstanding PRs, then cut a 0.3.0 release with the new features + fixes
  • review all open issues and close any that are now resolved by the new PRs
  • setup tests (a couple of e2e that uses karmas API and mocks nothing would be best)
  • setup eslint
  • setup travis that runs the tests and the linter
  • add more examples (TS karma preprocessor, system.js, anything else??) -> both of these come with remap istanbul integrated
  • upgrade remap-istanbul to latest -> waiting on 0.9.0 to land
  • drop support for node 0.12 (at the end of the year)

cc @mateuszjuszkiewicz @delasteve

@mat-82
Copy link
Collaborator

mat-82 commented Dec 6, 2016

PRs:

Issues:

As for releases, should 0.2.2 be cut first and 0.3.0 after tests prove that upgrade to remap-istanbul to 0.7.0 doesn't cause any issues?

@mattlewis92
Copy link
Contributor Author

@mateuszjuszkiewicz nice, thanks for doing that summary 👍

My thinking was to do a 0.3.0 release once #19 is merged (as it's a new feature which would be a minor bump according to semver). That will solve the immediate blockages for folks using this module. After that do the remap-istanbul upgrade, although it shouldn't be breaking according to the release notes

@e-cloud
Copy link

e-cloud commented Dec 7, 2016

I tried to upgrade to remap-istanbul v0.7.x in angular-cli. However, it's incompatible.

mattlewis92 pushed a commit that referenced this issue Dec 18, 2016
mattlewis92 pushed a commit that referenced this issue Dec 18, 2016
@mattlewis92
Copy link
Contributor Author

@marcules sorry to bother you, is there any chance you could enable this repo on travis? https://travis-ci.org/ Should only take < 1 min 😃

@marcules
Copy link
Owner

marcules commented Dec 20, 2016 via email

@mattlewis92
Copy link
Contributor Author

Awesome, thanks! 😃

@mattlewis92
Copy link
Contributor Author

@marcules any chance you could enable travis please when you have a sec? Thanks, and happy new year! 😃

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