Subscriber Login: Move Subscriber Login block to production

[pkuliga]

Part of #34884

Proposed changes:

It moves the Subscriber Login block to production.

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:

Make sure the Subscriber Login block is no longer marked as a beta block.

[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 Team Review, ...).
  
• ✅ 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 🤖

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Once your PR is ready for review, check one last time that all required checks appearing at the bottom of this PR are passing or skipped.
Then, add the "[Status] Needs Team Review" label and ask someone from your team review the code. Once reviewed, it can then be merged.
If you need an extra review from someone familiar with the codebase, you can update the labels from "[Status] Needs Team Review" to "[Status] Needs Review", and in that case Jetpack Approvers will do a final review of your PR.

---

Jetpack plugin:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen daily.
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly. The next release is scheduled for February 6, 2024 (scheduled code freeze on February 5, 2024).

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

[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 WordPress.com Simple 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, and enable the update/subscriber-login-no-longer-beta branch.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/subscriber-login-no-longer-beta
  

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

[jeherve]

If we're moving this block to production, would it be possible to let the WordPress.com and Jetpack support teams know, so they can work on the necessary support documents, and so they know what this new block brings to customers?

Thanks!

Also cc'ing @Automattic/jetpack-garage for general awareness for the upcoming release.

[samiff]

Also cc'ing @Automattic/jetpack-garage for general awareness for the upcoming release.

Thanks! For reference the hard cut for Jetpack 13.1 will be on 2024-02-05

Internal testing for Jetpack 13.1 has started this week, so if we want testers to give this a spin, you can either update the testing thread or let me know and I can assist: p8oabR-1qU-p2

[pkuliga]

Internal testing for Jetpack 13.1 has started this week, so if we want testers to give this a spin, you can either update the testing thread or let me know and I can assist: p8oabR-1qU-p2

Sure, I can do it. By "update the testing thread" you mean adding some testing scenarios below "Jetpack 13.1 Testing Items"?

[samiff]

By "update the testing thread" you mean adding some testing scenarios below "Jetpack 13.1 Testing Items"?

Yes! Any steps you think might be helpful in surfacing any bugs in the different testing environments.

[pkuliga]

Added 😄

p8oabR-1qU-p2#subscriber-login-block