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

Gutenberg: research spike for pulling in latest features to wpcom [3] #32291

Closed
vindl opened this issue Apr 15, 2019 · 1 comment
Closed

Gutenberg: research spike for pulling in latest features to wpcom [3] #32291

vindl opened this issue Apr 15, 2019 · 1 comment
Assignees
Labels
[Pri] High Address as soon as possible after BLOCKER issues [Type] Task

Comments

@vindl
Copy link
Member

vindl commented Apr 15, 2019

We need to research the possibility of cherry-picking required features from Gutenberg into WP.com codebase. Based on our previous experience, we'd prefer to avoid having to run a plugin and update it every two weeks, so this looks like the solution that could enable us to develop, test, and ship new features faster (not having to wait on 2 month cadence for core updates to land).

@vindl vindl added [Pri] High Address as soon as possible after BLOCKER issues [Type] Task labels Apr 15, 2019
@vindl vindl changed the title Gutenberg: research spike for cherry-picking features Gutenberg: research spike for cherry-picking features [4] Apr 19, 2019
@vindl vindl changed the title Gutenberg: research spike for cherry-picking features [4] Gutenberg: research spike for cherry-picking features Apr 19, 2019
@vindl vindl self-assigned this Apr 20, 2019
@vindl vindl changed the title Gutenberg: research spike for cherry-picking features Gutenberg: research spike for pulling in latest features to wpcom Apr 22, 2019
@vindl vindl changed the title Gutenberg: research spike for pulling in latest features to wpcom Gutenberg: research spike for pulling in latest features to wpcom [3] Apr 22, 2019
@vindl vindl added this to the WP-Lannister Sprint [17-18] milestone Apr 22, 2019
@vindl vindl closed this as completed Apr 22, 2019
@vindl vindl reopened this Apr 22, 2019
@vindl
Copy link
Member Author

vindl commented Apr 29, 2019

See #32624 (comment) for the suggested approach.

@vindl vindl closed this as completed Apr 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Pri] High Address as soon as possible after BLOCKER issues [Type] Task
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant