Subscribers: fix time since

[arcangelini]

Proposed Changes

Switch from Since subscribed to Date Subscribed in subscribers data view.

Why are these changes being made?

Currently the time difference from subscribed is checking against UTC time rather than the sites time. Adding the +00:00 to the subscribed date fixes that part.

I also don't think it is necessary to show "time since" in this area. There doesn't appear to be a reason that someone would need this detail over just the subscribed date. Moving this to just a simple date simplifies things I believe.

Testing Instructions

1. Pull the branch and navigate to /subscribers/YOUR_SITE.com
2. Check that the Date Subscribed column is showing the correct dates in the correct order.
3. Add a new subscriber and verify the order is still correct.
4. Change timezone on your site and make sure the order is still correct.
5. Change languages for your user and ensure it shows the proper date.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-146549

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-146549&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-146549&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~68 bytes added 📈 [gzipped])

name         parsed_size           gzip_size
subscribers       +114 B  (+0.0%)      +68 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• blaze-dashboard
• notifications

To test WordPress.com changes, run install-plugin.sh $pluginSlug fix/issue-cml-530 on your sandbox.

[Addison-Stavlo]

This tests well on my end. I just left some minor notes on the new translation.

[Addison-Stavlo]

I think technically we do all labels in sentence case now, although this is currently all caps in the interface here anyways. It may be good to move it to sentence case for consistency if the typography styles were changed.

It also doesn't look like we have existing translations for "Date Subscribed". So we could use the fixMe function from the i18n-calypso library to provide this new translation with the old translation as a fallback while the new one is being translated.

[arcangelini]

Great call! Thanks @Addison-Stavlo

[a8ci18n]

This Pull Request is now available for translation here: https://translate.wordpress.com/deliverables/17535013

Some locales (Hebrew) have been temporarily machine-translated due to translator availability. All other translations are usually ready within a few days. Untranslated and machine-translated strings will be sent for translation next Monday and are expected to be completed by the following Friday.

Thank you @arcangelini for including a screenshot in the description! This is really helpful for our translators.