-
Notifications
You must be signed in to change notification settings - Fork 813
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
Remove Jumpstart #12747
Remove Jumpstart #12747
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
@@ -3,6 +3,7 @@ | |||
/_inc/blocks | |||
/_inc/build | |||
/_inc/client/**/test/*.js | |||
/_inc/jetpack-modules.models.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ES5 file that was eslint-erroring a whole lotta. :-)
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: July 2, 2019. |
if ( ! Jetpack_Options::get_option( 'jumpstart' ) ) { | ||
Jetpack_Options::update_option( 'jumpstart', 'new_connection' ); | ||
|
||
$jetpack = Jetpack::init(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to investigate what was going on here and if jumpstart
option is used to somehow detect the state of Jetpack, not just state of Jumpstart? Update: probably not, says Derek
Need to investigate what's up with this:
Update: those lines can be removed, "recommended features" is synonym of jumpstart Update: removed lines |
@@ -93,7 +93,6 @@ public static function get_option_names( $type = 'compact' ) { | |||
'identity_crisis_whitelist', // (array) An array of options, each having an array of the values whitelisted for it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Noting that I got heaps of phpcs errors from this file and had to use --no-verify
to skip tests and commit:
FILE: packages/options/legacy/class.jetpack-options.php
----------------------------------------------------------------------
FOUND 39 ERRORS AND 10 WARNINGS AFFECTING 41 LINES
----------------------------------------------------------------------
....
I'd like early testing/reviews on this even tho I'd still consider it also to be in progress. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to work fine and some quick digging around doesn't reveal any leftover jumpstart code, although I'm sure there's some 🙂
I do think we need some careful consideration:
- What's enabled by default?
- What would have been enabled by jumpstart?
- What would be covered by the new checklist?
- How does the following the checklist differ from triggering jumpstart?
I'd like to have a clear understanding of the above written out so we can refer to this PR and have clear expectations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This tested well for me too. Would be happy to merge after resolving conflicts. |
c838df2
to
89b2c56
Compare
Rebased & removed lockfile changes |
Here's a list of tasks in the checklist — I'm adding ✅to those that were also enabled by Jumpstart:
Things that were always auto-enabled regardless:
|
simison, Your synced wpcom patch D29600-code has been updated. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This still looks good to me. Merging.
+16 −820 ❤️ |
* Remove Jumpstart * Add _inc/jetpack-modules.models.js to eslintignore * Revert lockfile change * Update build-module-headings-translations.php * Update composer.lock
Removing everything jumpstart related.
Basically informs me that I should first PR a change which just modifies minimum to hide Jumpstart from Jetpack, and then PR separately follow-ups to clean up the code.Got convinced by @dereksmart that this is solid. (p1560894750228800-slack-jetpack-dna). If further testing reveals surprises that take more than a day to fix, we can reassess and do the simple hiding instead.Jumpstart might normally get disabled once some module toggles are changed. (Will still need to confirm if this is the case). If so, should we keep Jumpstart for those who didn't activate any features in the checklist, @jeffgolenski?
See inline comments for some todos.
Resolves #12601
Changes proposed in this Pull Request:
Is this a new feature or does it add/remove features to an existing part of Jetpack?
Removes existing feature.
Testing instructions:
Proposed changelog entry for your changes: