惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

美团技术团队
Microsoft Azure Blog
Microsoft Azure Blog
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
B
Blog
Y
Y Combinator Blog
博客园_首页
有赞技术团队
有赞技术团队
博客园 - Franky
腾讯CDC
G
Google Developers Blog
Recent Announcements
Recent Announcements
博客园 - 【当耐特】
D
Docker
The GitHub Blog
The GitHub Blog
MyScale Blog
MyScale Blog
H
Help Net Security
Apple Machine Learning Research
Apple Machine Learning Research
A
About on SuperTechFans
D
DataBreaches.Net
T
The Blog of Author Tim Ferriss
V
V2EX
U
Unit 42
aimingoo的专栏
aimingoo的专栏
WordPress大学
WordPress大学

Danb Blog

August 2026: What I've Been Working On · Danb Blog Great Tech: Intel 2500k CPU · Danb Blog July 2026: What I've Been Working On · Danb Blog My Experience with Ubuntu Desktop 26.04 · Danb Blog Thumbnails for Orca 3MF in GNOME Files · Danb Blog Cheaper Sodastream Gas with a Big Tank · Danb Blog June 2026: What I've Been Working On · Danb Blog Running Snyk On Forgejo/Codeberg Actions · Danb Blog Tuta & Proton: An Open Source Client Does Not Result in an Open Source Service · Danb Blog May 2026: What I've Been Working On · Danb Blog 3D Printing Parts for my Greenhouse, Round 2 · Danb Blog Great Devices: Nexus 7 2013 · Danb Blog R36S Console RetroArch Stuck Menu Issue · Danb Blog April 2026: What I've Been Working On · Danb Blog Basic OpenCode Sandboxing with Docker · Danb Blog Games Played in 2025 · Danb Blog March 2026: What I've Been Working On · Danb Blog Shivam Mathur's "node-docker" Images are Awesome for PHP CI · Danb Blog February 2026: What I've Been Working On · Danb Blog Your BookStackApp project was assigned as a project for my Software Architecture course · Danb Blog My Sovol SV08 3D Printer Setup in 2026 · Danb Blog January 2026: What I've Been Working On · Danb Blog Epson Printer: The administrator password you entered was not recognized · Danb Blog Pressure to Follow Process · Danb Blog Online Shopping Email Notifications · Danb Blog My HomeLab Setup in 2026 · Danb Blog Linux Label Printing with the Phomemo D30 · Danb Blog Reporting to the CMA: Google Android Developer Verification · Danb Blog OPNsense & Dnsmasq: Responding with specific DNS servers · Danb Blog An Impromptu Introduction to ZFS Drive Replacement at 1am · Danb Blog
A Thanks to Laravel for the LTS Releases · Danb Blog
2020-12-09 · via Danb Blog

8th of December 2020

I just wanna shout my thanks to Taylor Otwell, Graham Campbell, Mohamed Said, Dries Vints & all the other great Laravel maintainers for spending the time and effort in maintaining the LTS releases of the framework (In addition to all the other work you do for the framework and it’s ecosystem).

On Reddit & Twitter I commonly see the LTS releases being referred to as an anti-pattern with a general recommendation to avoid, which I can sort of understand in the view of most common use-cases of Laravel, but I want to share how the LTS releases have a benefit for me.

I maintain BookStack, a Laravel-based project started in 2015 with steadily growing popularity. The project is maintained completely in free-time by myself and others in the community. As with most growing open source projects, with growing popularity time has become more limited as effort is spent on issue management, helping users and maintaining the project itself.

Evolving and upgrading the framework is of course necessary to keep up with technology and ideas. For the project I see two main costs on upgrading to a newer version of Laravel:

  1. The time spent updating the codebase.
  2. The time spent supporting the user-base with requirement changes from the framework upgrade.

In regards to 1, the LTS releases don’t really have a large impact other than being able to wait before then upgrading through multiple versions in one hit, which is more efficient but the time saving is relatively insignificant.

In regards to 2, this is a big deal for me. New versions of the framework often come with slight requirements changes, mostly the PHP version. For this we need to update install scripts, document ways to upgrade existing installs and support any issues raised by our users. While it does not seem like a lot, this can consume a surprising amount of time that would be better spent on the application itself. Being able to have this on a 2 year, instead of 6-month, cadence while receiving bug & security fixes is a big deal which allows me to focus on the code, on the framework which I love.

So, Thanks.