@JeffreyWay - you are right, of course. I like to think of myself as one of the more moderate responders on this forum ... and I tell you I am more than a little concerned.

Out of interest, how much time have you budgeted to upgrade Laracasts to L5?

@JeffreyWay Ok, I stand corrected on semver. Thought that was the reason.

It's not a global thing. This particular release was originally supposed to be modest in scope.

As for "best interests of the framework", who would say no to that? You can justify anything as being "in the best interests of the framework".

I agree with you, Jeffrey, this release is more massive than originally thought. This is my first Laravel release cycle, so since the action really picks up towards the end of the release cycle, I'll just let the cycle transpire before digging in. Lesson learned!

What I find interesting is that the thread comments really showcase why open source is both great and horrible. :)

If Laravel were a paid product we, as users, would never see or get access to the code before it's "officially" ready. But since it is open you are free to use it and watch the progression and participate in it. Which is awesome!

Early adopters always get the "new shiny stuff" but it always comes at a cost. To give an example I updated my phone to early iOS8 beta months ago. Every 20 minutes it would crash or just do weird stuff. After a few days I just gave up and reverted back which was a really annoying process.

In the end I don't really get all the negativity around this. There is still plenty of time for it stable out, an upgrade routine to be outlined, and everything else that goes with an official release.

I think it is pretty obvious: these changes were 4.3! Most of us working with L5 are doing so because it was originally 4.3. That's why I'm frustrated - if I knew it was going to be a major version change I would have waited. But, now I'm stuck.

That being said, I'm very excited for L5!

As a note of caution, throughout this thread a few posts put words in other's mouth. My suggestion is to let others speak for themselves.

You can always lock the version you are working on to a specific commit. So if you don't know how to fix something (yet), just keep on the version you have working.

If you try to drive your car out of the garage before the wheel nuts have been tightened, the wheels are going to fall off

We'll talk about this during the Laravel podcast today.