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

misc: add instructions about test release #2486

Merged
merged 11 commits into from
Apr 2, 2020
Merged

Conversation

lex111
Copy link
Contributor

@lex111 lex111 commented Mar 31, 2020

Motivation

Reduce the possibility of releasing a "bad" version that will make us hurry and nervously fix it as a hot fix :(

The point is a simple one: before the release of the new version, we build all the packages and try to run the website with them. To make everything as close to reality as possible, we publish the packages in a local private npm registry Verdaccio and only then use them for testing purposes.

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

See instructions. Tested on Linux, but should work on Mac.

Related PRs

(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

@lex111 lex111 added the pr: maintenance This PR does not produce any behavior differences to end users when upgrading. label Mar 31, 2020
@lex111 lex111 requested a review from yangshun March 31, 2020 13:24
@facebook-github-bot facebook-github-bot added the CLA Signed Signed Facebook CLA label Mar 31, 2020
@docusaurus-bot
Copy link
Contributor

docusaurus-bot commented Mar 31, 2020

Deploy preview for docusaurus-2 ready!

Built with commit ea4848e

https://deploy-preview-2486--docusaurus-2.netlify.com

@lex111
Copy link
Contributor Author

lex111 commented Mar 31, 2020

It looks like the Verdaccio dependencies in the root workspace affect the rest of the dependencies (including v1). Can we use Docker to run a private proxy?

@yangshun
Copy link
Contributor

I don't think we have time to get this working before our next release

@lex111
Copy link
Contributor Author

lex111 commented Mar 31, 2020

Sure, it can wait. I think it's best to use Docker here.

@lex111
Copy link
Contributor Author

lex111 commented Apr 1, 2020

I updated the instructions, now we only need to execute one command (but Docker installed is required). It is OK?

@yangshun
Copy link
Contributor

yangshun commented Apr 1, 2020 via email

@lex111
Copy link
Contributor Author

lex111 commented Apr 2, 2020

@yangshun ready for review!

Copy link
Contributor

@yangshun yangshun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will need docker installed on my computer to test the command?

@lex111
Copy link
Contributor Author

lex111 commented Apr 2, 2020

Of course!

Copy link
Contributor

@yangshun yangshun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok sure, might want to add instructions that docker has to be installed.

@lex111
Copy link
Contributor Author

lex111 commented Apr 2, 2020

I think you can easily googled installation instructions for Docker, especially as this sort information may change over time.

@yangshun
Copy link
Contributor

yangshun commented Apr 2, 2020

I don't mean the installation instructions. Just mention that we need Docker installed. Because it's not obvious from the instructions unless I read the script.

@lex111
Copy link
Contributor Author

lex111 commented Apr 2, 2020

Ah sure, added this to the heading.

@yangshun yangshun merged commit 18d31b5 into master Apr 2, 2020
@yangshun yangshun deleted the lex111/test-release branch April 2, 2020 07:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Signed Facebook CLA pr: maintenance This PR does not produce any behavior differences to end users when upgrading.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants