Launch Laravel Laravel Package

Product Decisions This Supports

• Supports a build-vs-buy decision for Laravel launch/pre-launch workflows: v0.3.10 moves route registration to native Laravel route files, reducing reliance on the Waymaker abstraction and making the package easier to evaluate against standard Laravel conventions.
• Useful for MVP and early-access roadmap decisions where speed matters and the team wants framework-native routing rather than a custom route-loading dependency.
• Helps assess maintenance risk: replacing a third-party routing layer with Laravel route files can simplify customization, auditing, and onboarding for Laravel engineers.
• Does not indicate a new customer-facing feature; the release is primarily an internal architecture change. Product prioritization should treat it as a maintainability/compatibility improvement, not a roadmap feature.

When to Consider This Package

• Consider it when you need a Laravel-native package for launch/pre-launch functionality and prefer standard route files over custom route registration mechanisms.
• Consider it for internal tools, MVPs, or early-stage products where a pre-1.0 package is acceptable and version pinning plus regression testing are in place.
• Validate upgrade impact if you have customized routes or relied on Waymaker-specific behavior; replacing the routing mechanism may affect route loading, overrides, or package integration points.
• Look elsewhere or wait for a 1.0 release if you need stable public APIs, long-term support commitments, enterprise SLA, or a broad feature set with predictable upgrade paths.
• Avoid adopting solely for this release if you require new product capabilities; v0.3.10 is a routing refactor, not a feature release.

How to Pitch It (Stakeholders)

• Executives: this is a small, Laravel-native dependency that can reduce custom glue code for launch-related workflows. The latest release simplifies routing by using standard Laravel route files, which lowers long-term maintenance risk but does not add a major new feature.
• Engineering: v0.3.10 replaces Waymaker with Laravel route files. That aligns the package with framework conventions, makes routing easier to inspect and customize, and removes an intermediate dependency. Pin the version and run route-loading/regression tests, especially if you override routes or depend on Waymaker behavior.
• Product: treat this as a stability and maintainability signal, not a reason to re-plan the roadmap. It supports continued evaluation for MVP/launch use cases while the package remains pre-1.0.