0.9.4 and 0.10.0 roadmap

[gaearon]

Let’s discuss the next releases.

0.9.1

Hi Pri

For 0.9.1, I feel strongly we should release it asap so that we can land more breaking changes without cherry-picking stuff. In particular I want to see these fixed:

• Figure out how to deal with slashes in Jest: Jest does not validate <rootDir> reference in some environments #1417, eject command on windows creates different path sepalators to package.json #1498. This should be easy to fix—perhaps it's enough to just use forward slashes everywhere. I just want to make sure we test this works on Windows, and fix it once and for all. I’m happy to test any given PR on Windows if you think you have something that should work and just need confirmation.

• Fix npm link for people who fork react-scripts Fix workflow if react-scripts package is linked via npm-link #1356

• Gracefully handle installation failures Gracefully handle initial installation error (#1505) #1512

Lo Pri

I don't feel strongly about these ones:

• Jest.mock does not resolve modules correctly when NODE_PATH is set (Jest.mock does not resolve modules correctly when NODE_PATH is set #1271).

• CSS dependency with private module @import fails (CSS dependency with private module @import fails with #1290)

• npm version check (NPM version check for tip #1193)

• Some e2e test failure with forking react-scripts. e2e tests fail because of missing package.json #1401. Should be easy to look into and decide.

We could postpone looking into them until 0.9.2 or 0.10. I don't want them holding off 0.9.1 release.

0.9.4

Bugs:

• Jest.mock does not resolve modules correctly when NODE_PATH is set (Jest.mock does not resolve modules correctly when NODE_PATH is set #1271).

Things we should stabilize before the next breaking release, but not necessarially blocking (this would have to be in 0.10):

• CSS dependency with private module @import fails (CSS dependency with private module @import fails with #1290)

We want to make tracking react-scripts painless:

• Some e2e test failure with forking react-scripts. e2e tests fail because of missing package.json #1401. Should be easy to look into and decide.
• Scoped packages should work with our CLI: Scoped packages on forked versions #1414

0.10.0

There's a lot of stuff there to still get in.

I want to merge #1101 and release a canary so that people can start playing with it (cc @kittens). It shouldn't be an official release because we still have a bunch of known issues with 0.10.

After we cut 0.9.1 0.9.4 we can write a clearer roadmap here.

Plan

I guess at this point we just need somebody willing to get 0.9.1 to the point where it’s ready. @Timer Could you do this? Alternatively we can ask somebody else to help with the release, or maybe I could give it some time next week.

We should focus on stabilizing and releasing the final 0.9.x release, then begin focusing on 0.10 and addressing all the underlying bugs which are blocking us, performing upstream reporting & triaging where necessary.

[Timer]

I've been slowly (maybe too slowly) chopping down the issues for 0.9.1 in my spare time. Now that the weekend is here, I hope I can push it the rest of the way.
Given those lower-priority issues, I feel like it's much easier to cut 0.9.1.

As for someone else helping, more is always merrier.

[gaearon]

Thanks for your help! I merged a few hanging PRs and I think we're pretty close to cutting 0.9.1 now.
I also retagged postponed issues to 0.9.2 and 0.10.

[Timer]

0.9.x should be ready to cut, I believe all non 0.10.x commits are cherry-picked (and I hope no 0.10.x were picked into 0.9.x):
< being 0.9.x, > is master.
The 3 are showing up as new on 0.9.x because they required merging and were not a direct patch translation.

I would appreciate you signing off on bf11b14 -- 0a41334 and 627e67d are pretty trivial.

Joes-MacBook-Pro:create-react-app joe$ git co master 
Switched to branch 'master'
Your branch is up-to-date with 'origin/master'.

Joes-MacBook-Pro:create-react-app joe$ git compare 0.9.x
< bf11b14 Enable eslint caching in development (#1578)
< 627e67d Bump `recursive-readdir`. (#1560)
< 0a41334 babel-preset: remove babel-plugin-transform-es2015-parameters (#1598)
> 2288ddf Support & test import() for non-bundled code (#1615)
> 8d41328 Enable eslint caching in development (#1578)
> dd801e2 Disallow event global variable with no-restricted-globals rule (#1530) (#1532)
> 41d1469 Bump `recursive-readdir`. (#1560)
> 09cfcde Add lint rule to disallow require.ensure and System.import (#1536)
> 0ef9e80 (feat): add webpack validation error logging (#1596)
> 21fe19a Bump deps for webpack 2 compat (#1621)
> 1aa4b2b babel-preset: remove babel-plugin-transform-es2015-parameters (#1598)
> 41632fb Revert "Bump babel deps and re-enable transform-react-constant-elements" (#1575)
> 9c33f60 Re-enable transform-react-constant-elements (#1552)
> 1d5a277 Enable `watchContentBase` for webpack-dev-server (#1546)
> fc49946 Add support for dynamic import & disable require.ensure (#1538)
> 1228883 Upgrade webpack (#1291)

[gaearon]

Looks good, thanks for cherry-picking!

[Timer]

Good to cut a release?

[gaearon]

👍

[shai32]

@gaearon Do you plan to update the roadmap?

[gaearon]

So far 0.10 issue list should be a good reference. We may postpone some of these, but there are critical bugs that need to be fixed. Want to help with any of these issues?

[Timer]

I went ahead and updated the roadmap (in the most basic form). We can write a detailed plan for 0.10 once we cut 0.9.4.

[Timer]

Closing this since we're working on a new umbrella issue planned to land today ...