Statamic Opening Hours Laravel Package

Product Decisions This Supports

• Build vs. buy: Quantifies the maintenance burden of replicating functionality in-house versus adopting and upgrading this package. v3.0.0's breaking changes are a forcing function for this calculation — estimate upgrade effort against the cost of a parallel internal build.
• Roadmap sequencing: v3.0.0's breaking changes create a hard dependency for any roadmap item that relies on pinned v2 behavior. Flag affected epics and re-sequence around the upgrade window before committing dates.
• Version support policy: Use the major-version jump to decide whether the team supports one or multiple minor lines, and whether to adopt "latest major only" or "N-1 lag" as a standing policy for PHP ecosystem dependencies.
• Feature prioritization: New capabilities in v3.0.0 map directly to candidate features. Compare against backlog demand to decide what to ship "for free" via upgrade versus what still needs custom work.
• Deprecation debt tracking: Every deprecated API in this release becomes a line item in the tech-debt register with a target removal version. This gives leadership a visible, bounded migration plan rather than an open-ended risk.
• Use-case fit: Validates (or rules out) specific product scenarios — the package's current capabilities define the ceiling of what the team can ship without custom code for this domain.

When to Consider This Package

Adopt when:

• You are starting a new Laravel service and need standard functionality this package provides out of the box.
• The package is actively maintained with clear semantic versioning and a documented changelog/upgrade guide (this v3.0.0 release should include one; confirm before committing).
• Your Laravel and PHP versions fall inside the package's supported matrix.
• Time-to-market outweighs the strategic value of owning the implementation.
• The team lacks deep in-house expertise in the domain and benefits from an opinionated, community-tested implementation.
• The license is compatible with your distribution model (including any SaaS/server-side use).

Look elsewhere when:

• Your requirements are highly bespoke and would require forking or heavy overriding — the maintenance savings evaporate.
• The package has a history of undisciplined breaking changes, or v3.0.0 ships without a migration path.
• The dependency footprint pulls in conflicting transitive packages or locks you to an unsupported Laravel version.
• You need long-term support beyond what the maintainers commit to (evaluate a paid support tier or a maintained fork first).
• Regulatory, licensing, or security review flags concerns not addressed in the release.

How to Pitch It (Stakeholders)

For executives: This package lets us ship a set of standard capabilities without building them ourselves, compressing time-to-market and lowering cost. The v3.0.0 release is a maintenance event, not a new cost center — but it requires a scoped upgrade window and a small allocation of engineering time. The decision is whether to invest that time now (recommended) or accept growing risk by staying on v2. We should treat the upgrade as a planned, bounded initiative with a clear owner and deadline.

For engineering: v3.0.0 introduces breaking changes and deprecations that affect our integration points. Adopting the package is the right call for standard use cases, but we need an upgrade guide, CI coverage against the new version, and a deprecation cleanup ticket tracked alongside feature work. Recommend a feature-branch upgrade spike to size the effort before committing the team, and pin the current major until the migration is verified.