For sites that require modules to be covered by the Drupal security team, using this module is currently a no-no.

What, if any, are the barriers to making a full stable release with security coverage?

Issue fork daterange_compact-2887927

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

John Pitcairn created an issue. See original summary.

johnpitcairn’s picture

johnpitcairn commented
Issue summary: View changes
erik.erskine’s picture

erik.erskine commented

This module needs to pass the review process first.
Linking to that issue for reference: #2875485: [D8] Compact date/time range formatter

johnpitcairn’s picture

johnpitcairn commented

Thanks, I did RTBC that issue. Hopefully one of the queue maintainers will grant you the appropriate status to opt in to security coverage, I'm not able to do so.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

What about joining forces with https://www.drupal.org/project/date_range_formatter, which has a stable release?

hanness’s picture

hanness
Primary language German
commented

#2875485: [D8] Compact date/time range formatter is fixed now and beside one RTBC bug (#2970628: Add support for optional end dates) there are only feature requests with normal priority in the issue queue.

So +1 for a stable (or at least beta/alpha) release.

dww’s picture

dww
we/he/they
commented
Status: Active » Postponed
Parent issue: » #2834016: Add 'Compact' datetime range formatter

Looks like the maintainer would rather merge this into datetime_extras:

#2834016: Add 'Compact' datetime range formatter

We'll move this issue into that queue for an official release of datetime_extras once this formatter lands (and potentially we clean up a few more things).

If that happens as proposed, we'll move all the issues out of this queue into there.

Stay tuned,
-Derek

johnpitcairn’s picture

johnpitcairn commented

Frankly I'm not sure that will help us - datetime_extras doesn't have a stable version either, and I think I remember there was some kind of statement a while back that it may never have one.

dww’s picture

dww
we/he/they
commented

Yeah, the way datetime_extras is currently maintained leaves something to be desired. ;) I'm rethinking it, myself. I might just add my own project for #2845081: Provide a datetime_range widget to define end time via a duration offset since it's unclear if/how it's going to work to include it in datetime_extras, if they're just going to give me commit access to keep it moving forward, etc.

BarisW’s picture

BarisW commented

Can we have a release please? Thanks!

erik.erskine’s picture

erik.erskine commented
Assigned: Unassigned » erik.erskine
Status: Postponed » Active

Re-opening this, we have a plan to get it moving forward again.

After discussion with @dww in #3213646: Datetime Community meeting on May 13, 2021 it would seem to make sense to keep this functionality as a contrib module in it's own right.

It will include the functionality changes listed in #2834016: Add 'Compact' datetime range formatter, namely not having separate settings for date & datetime. That change breaks BC with existing code, so this will be a 2.0 release and the 1.x branch will be abandoned.

dww’s picture

dww
we/he/they
commented

Sounds good, thanks! Sorry I wasn't able to help get #2834016 into datetime_extras. #LifeIsComplicated

While we're at it, let's switch this project to semver, make the new branch for this work 2.0.x and tag things towards a 2.0.0 release.

Thanks again,
-Derek

erik.erskine’s picture

erik.erskine commented

2.0.0-beta1 is available, feedback appreciated.

erik.erskine’s picture

erik.erskine commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.