Forms: release rating and slider fields for WP.com customers

[simison]

Proposed changes:

• Releases new "ratings" and "slider" form fields for WP.com customer by changing them from "beta" blocks to "experimental" blocks.

jetpack/projects/plugins/jetpack/extensions/README.md

Line 109 in 4ec0394

Experimental extensions are usually considered ready for production, but are served only to sites requesting them. **All WordPress.com sites have access to experimental extensions**.

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

Does this pull request change what data or activity we track or use?

Testing instructions:

• Without define('JETPACK_BLOCKS_VARIATION', 'beta'); configured, blocks should not be available on Jetpack
• At WP.com blocks should be available
• Try the slider and ratings once more

[github-actions]

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

• To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the update/forms-release-rating-slider branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/forms-release-rating-slider

Interested in more tips and information?

• In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
• Read more about our development workflow here: PCYsg-eg0-p2
• Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

[github-actions]

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

• ✅ Include a description of your PR changes.
  
• ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  
• ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  
• ✅ Add testing instructions.
  
• ✅ Specify whether this PR includes any changes to data or privacy.
  
• ✅ Add changelog entries to affected projects
  

This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
3. You can use GitHub's Reviewers functionality to request a review.
4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!

---

Jetpack plugin:

No scheduled milestone found for this plugin.

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[jp-launch-control]

Code Coverage Summary

Coverage changed in 1 file.

File	Coverage	Δ%	Δ Uncovered
projects/packages/forms/src/blocks/contact-form/class-contact-form-block.php	285/589 (48.39%)	0.18%	0 💚

Full summary · PHP report · JS report

[edanzer]

Code changes look straightforward. In my local dev environment, I tested to confirm that the slider and rating blocks only show when the block variation is set to experimental.

I wasn't quite sure how to test this on WordPress.com. Usually proxy a test domain and load this branch in your sandbox to test. But as soon as you proxy and access WordPress.com, both beta and experimental version show. I did confirm these blocks still show in this branch. But I can't confirm they will now show for other users who are not proxied, which they should.

In any case, this seems safe to merge.

Great to move these one step closer to full release!