3 ms·
> Major framework releases are released every six months... Two major versions with breaking changes per year? This seems a bit too fast paced for my taste. B
by hu3 7y ago
> Major framework releases are released every six months...
Two major versions with breaking changes per year? This seems a bit too fast paced for my taste.
But I haven't used the framework and would love the input of someone that had to maintain a Laravel project for more than a year.
- nicoburns 7y ago> Two major versions with breaking changes per year? This seems a bit too fast paced for my taste. They provide LTS releases (similar to Ubuntu). I'd definitely recommend sticking to them for projects that are / will be in maintenance mode. The breaking changes are usually minor, so for actively developed projects, using the regular versions is fine.
- micael_dias 7y agoYou can also use https://laravelshift.com/ https://laravelshift.com/. I always manually updated using the documentation upgrade guide and never had a problem which will apply to most people who don't use internal undocumented functions.
- yurishimo 7y agoThe changes in each major version are pretty small. They’re sticking to semantic versioning now so if there is a major version bump, it’s likely a small change to some internal library that would only be breaking in the technical sense. Plus, this is the pace the framework has adopted for a long time now so most of the devs in the ecosystem are used to doing an upgrade once or twice a year. Generally they’re very quick. < 15 min.
- wishinghand 7y ago> They’re sticking to semantic versioning now I will believe that when I see it. edit: to clarify, historically they've bumped the minor version number whenever they had major changes in the API, and now the major version bumps are usually non-breaking changes. I don't think the team fully understands Semver.