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

Guides - Migrating from v2 to v3 #1569

Closed
zzzgit opened this issue Sep 4, 2017 · 2 comments
Closed

Guides - Migrating from v2 to v3 #1569

zzzgit opened this issue Sep 4, 2017 · 2 comments

Comments

@zzzgit
Copy link
Contributor

zzzgit commented Sep 4, 2017

image

there is a section for migrating from v1 to v2, but how about from v2 to v3?

@zzzgit
Copy link
Contributor Author

zzzgit commented Sep 4, 2017

i want to update webpack in my project from 2 to 3,but i can not do this hastily without a instruction

@skipjack skipjack changed the title is there some tips for Migrating from v2 to v3 Guides - Migrating from v2 to v3 Sep 5, 2017
@skipjack
Copy link
Collaborator

skipjack commented Sep 5, 2017

@zzzgit currently we only have the document for migrating from v1 to v2. This is because there were a lot more breaking changes from v1 to v2 than from v2 to v3. In fact, I migrated a bunch of projects to v3 without having to make any major configuration changes.

I would recommend just reviewing release notes for v3 and see if there's anything flagged [breaking change] that would affect your setup.

We do have a note in the current guide to note this:

image

I agree that this is slightly confusing and, long term, I think we should resolve this in one of two ways:

  • Remove the Migrating from v1 to v2 guide and push these articles to blog posts instead as they become dated very quickly with new releases. We could even add a redirect to the blog post for the removed guide.
  • Rename this guide Migrating Versions and include notes on the breaking changes for each major release.

Frankly, I would lean towards the first option (and continue to improve on release notes) as it's been hard enough just to maintain our core guides/content. I'm going to close for now as we do already have a note in that guide but I'm marking with a reconsider label so we can revisit it later on. Our main goal right now is to continue cleaning up and restructuring the existing content (e.g. #1258 and others) and fixing some dev/infrastructure issues (#1525 and #1400).

@skipjack skipjack closed this as completed Sep 5, 2017
skipjack added a commit that referenced this issue Sep 6, 2017
Update the title and add small warning about where to look for
future migrations.

Related to #1569
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants