Will there be Laravel 4.2 support even after L5 released?

What level of support? I'm sure critical security vulnerabilities will be taken care of, for sure, but I wouldn't expect any new features being added.

Laravel 3 still "works". Depends what you mean by it though.

I think the team is struggling with getting L5 bug free, so I can't hope to see any L4 bug fixes.

Thanks guys for the feedback

"just started a project with laravel 4.2 not knowing that laravel 5 was right around the corner"...

I must ask, how long have you been following Laravel?

L5 didn't appear out of nowhere and has been some time coming. "Which rock..." springs to mind :)

@vincej - have you experienced any bugs with L4? - or L5 since actual release? That just seems a bit of a brash/blasé comment to make from someone with little real experience.

Regarding support for L4, Taylor has recently commented that L4 will still be supported somewhat, particularly with any security issues. just don't expect new features.

@sitesense umm ... where do you get your ideas from ?? yeah sure, I'm learning Laravel but that does not make me a fool. So I would appreciate that you ask me a question first, before assuming I could not possibly be right.

For your information, I spent 2 days last week discovering a considerable bug in L5. So much so that it kills the system dead when you try to upgrade your L4 code to L5. Don't believe me ? Check this out. Credit to @nolros who confirmed the bug: https://laracasts.com/discuss/channels/general-discussion/upgrading-to-l5-and-getting-class-not-found-on-composer-update/?page=3

That is not a bug of Laravel. It is a change of how Laravel work and use Namespace... There is no simple way to port your code from Laravel 4 to Laravel 5... You need to do it step by step carefully. That's why it is Laravel 5 and not 4.3...

@asakurayoh and @ sitesense I think Vince point is legit, finite resources with lots of moving parts, That said, the only people that comment on what are bugs or when they will be fixed is Taylor and team.

Also, agree on the no easy port,and cannot comment on bugs in ports as I'm running vanilla 5, but the issues Vince were facing were vanilla L5.

There are L5 bugs, to be expected, I would say a VERY solid release, but if you read the Laravel 5 github issues section you will see confirmed bugs. Example, there is a namespace bug and there are other issues with artisan, which is to be expected as it is fresh out. As of yesterday it was don't use "App" in namespace. Second, I can see the problem in services.json as to how it writes eager and deferred providers, and such I can remove the issue and recreate it again. Simply put if the a provider writes the services.json file the app runs fine with all the same code, if artisan writes the file and it runs into certain conditions or issues, such as, namespace, some decorators, etc. it will add the provider as deferred, in some cases replace the core class with the decorated class and also create a when condition that will fail silently. If an app run fine when the provider creates the services.json, but if artisan creates it it fails, that is a bug or at very least an undocumented feature. That said, it might not be a bug, it might be something else, but we share in the hopes of learning so I suggest have a calm informed dialogue.

@sitesense umm ... where do you get your ideas from ?? yeah sure, I'm learning Laravel but that does not make me a fool. So I would appreciate that you ask me a question first, before assuming I could not possibly be right.

@vincej My ideas of what?

I can only assume that you're referring to my comment about your lack of experience with Laravel. Well I get that idea from your posts. I made no suggestion that you're a fool. I myself have little experience with Laravel.

Further, I did ask you a question - what bugs have you found in Laravel 4 (or 5) to make such a statement that L4 won't be supported?

As for "assuming that you could not possibly be right", well Vince, you are in fact wrong. Taylor has stated that L4 will still get bug fixes.

So you found a "bug" in L5 whilst porting your L4 code. Sorry it didn't go perfectly for you first time and it wasn't documented. That doesn't mean that Laravel is unsupported though.

@sitesense This forum is not Stackoverflow. We don't need sniping or little put downs. On Laracasts I have found that those with the highest awards also have the most generous attitudes towards those of us who are learning. Thank you.

@vincej - You do make me chuckle each time I read your posts. For that I thank you :)

To accuse me of "sniping" after the childish quip that you made against Laravel because you've hit a stumbling block, is another classic!

Quote:

I think the team is struggling with getting L5 bug free, so I can't hope to see any L4 bug fixes.

@sitesense - you can't help your self with your little put downs, can you.

My original point should not be contentious.

Here are the facts:

1. L5 has bugs in it. Some are show stoppers. Like the one that I found and confirmed through the generous work of nolros. Maybe this morning another post about L5 mail.
2. Laravel has a limited development team.
3. The future of Laravel is L5. The past is L4.
4. L4 is reasonably stable.

Yes, it is obvious and does not need repeating that Taylor et al will deliver security updates. Where does it make sense to focus your limited dev resource - L4 or L5 ? How much resource does L3 get ? I would hazard a guess between zero and nil. Enough already, my original post is not that interesting.

Sorry @vincej I should have realised that this would blow up into a big debate before I pulled you up on the post.

So of course you're right! My bad. Have a good day.

@sitesense By Gones. I see you are a Brit. Me too. Hertford Town.

All the hating. You guys are tearing this family apart!!! This is why we cannot have nice code ... lol

btw, I found this on someone's forum post which I thought was a brilliant - "Real programmers don't comment their code. If it was hard to write, it should be hard to understand.‏ "

Real programmers don't comment their code. If it was hard to write, it should be hard to understand.‏

I completely and wholeheartedly disagree with that and thankfully most solid devs disagree with that also.

I think the team is struggling with getting L5 bug free, so I can't hope to see any L4 bug fixes.

I also to a point agree with @sitesense, more on the way you (@vincej) posed your statement and it's not the first you've made comments like that.

As far a judging skill based on points and awards a person awards on laracasts, that's not at all solid way of defining a person's skills. It just shows that they participate more. i.e., you have more points and awards than several people on here who have some seriously mad skills.

To the OP, @dylanYP, Taylor has said on several occasions that L4 will receive bug-fixes. Also it has a very large community behind it that will continue to support it. Not everyone is make the move to L5 just because it's out.

@dberry I don't know why you would wish to bring this up. I thought this was put to bed.

it's not the first you've made comments like that.

What exactly are you talking about ? I make every effort to be exceptionally thankful for the generous help I have received from those who have helped. If you have 1 single additional example, I would be glad to see it. 99% of my comments are "how to .." questions.

With respect to my comment relating to a bug in L5. This is a statement of fact. Perhaps unpalatable, but real. Also real is the current questionable quality of the L5 docs shared by many. When you are student of L5 and you waste 2 whole days, as I did last week, assuming that you are the one at fault, when in fact the docs are flawed as too the code I think I have earned the right to pass a single 1 line comment without put downs ... no ?

Lastly, I celebrate the courtesy, time and skill of those people at the very top of the leader board who are prepared to assist a Laravel newb like me without making me feel small. There appears to me to be a correlation between those at the top award points and generosity of spirit.

I think this topic has been thrashed to death.

@vincej

I think the team is struggling with getting L5 bug free, so I can't hope to see any L4 bug fixes.

If this is being 'exceptionally thankful' towards the Laravel team, it's such a shame.

Also, if you think that others have thrashed this topic; if I were you, I would take another look at your original post.

Does it not strike you as odd that you seem to magically attract this negative attention. You keep bashing on the Laravel community for being less experienced than you, just because you are of age. I think it's appalling how you have been addressing other community members recently.

I've always been told that the best way to grow is to open up to criticism, and right now all you're showing us is that you're extremely closed off (even when most of us are really just trying to make you aware of your behaviour).

Regards

@jacob I would like you to add value. Go back to my original post in this thread. Reread all the materials relating to the bug I found and the docs that surround it. Read the investigation which Nolros undertook ( btw he is "old" too ). Test this for yourself as Nolros did. Then and only then please come back to me and tell me your findings. Tell me also that it is not a bug and that Nolros and myself are wrong. Tell me also please how to work around it. Then I will listen carefully and you will have my unqualified respect as does Nolros, Bashy, Bestmomo, Pmall et al.
Many thanks for all your efforts !

@vincej what are you trying to prove here?

The OP asked whether to expect bug fixes for L4 now that L5 is out. That has now been answered no thanks to you.

You replied, offering zero value and being factually incorrect, with a "butt hurt" statement that "the Team" can't even get L5 in order, let alone L4.

Now you're turning it into a debate on whether or not L5 has bugs, seemingly in an effort to justify your crass statement.

You know, pretty much all software has "bugs", take a look at the "issues" with Symfony on Github for example.

The way you tackle issues is astounding and often offensive. Just look at your issue report on Github, it's almost too embarrassing to read:

https://github.com/laravel/framework/issues/7302

As someone who is totally incapable of dealing with criticism, you certainly don't mind dealing it out. Your sense of self-importance is also overwhelming.

... Then I will listen carefully and you will have my unqualified respect

I don't believe anyone here is looking for your respect, in fact most are probably pulling their hair out after trying to help you overcome the "schoolboy errors" that constitute the vast majority of your posts. Of course these aren't "your" errors, it's the documentation, or the video, or conflicting advice.

Sorry Vince, but I think you need to step down from that pedestal that you put yourself on and deal with reality.

@sitesense

Thanks for your comment: go back, read the original post where in I describe the error and nolros's confirmation and add value. Have a nice day.

@vincej ... I don't know, is it denial?

This is not about "your bug". This is not even your thread.

You keep saying read the OP - this IS THE OP.

https://laracasts.com/discuss/channels/general-discussion/will-there-be-laravel-42-support-even-after-l5-released/

@sitesense

My original post - provided at the beginning of this stream.

Now read second paragraph from the bottom. Nolros: "yes definitely a bug"

https://laracasts.com/discuss/channels/general-discussion/upgrading-to-l5-and-getting-class-not-found-on-composer-update/?page=3

@vincej

You're very caught up on your little 'find' that you're too blinded by the hate you're bringing to this community

For somebody who claims to be mature and experienced, you sure have a way to avoid questions that may deem you in the wrong.

I could not care less about your 'bug', though I doubt it is even that. And don't bother explaining to me that other developers have 'confirmed' it.

Your markdown skills are impeccable, I wish I could bolden the words 'add value' like you can. Seriously dude, understand that you're part of a community that wants to grow. Growth can only be accomplished if you throw away your own biases, and contribute in healthy discussion.

Regards

@jacob thank you for your comment. Have a nice day.

@vincej

What you could do is be the bigger man here, and admit that what you've said is hurtful and demoralising.

Or you can continue to say these things, and let everybody come up with their own opinion of you - of which I'd assume mainly negative.

I don't mean to knock you down, but right now it would seem you're attempting to deliberately harm the people of this community - Laravel, and also Laracasts.

Doesn't it seem easier to say one little 'sorry' and be forgiven, rather than causing many people to dislike you before they even get to know you?

I would assume that you would at least know this by now.

Real programmers don't comment their code. If it was hard to write, it should be hard to understand.‏

I completely and wholeheartedly disagree with that and thankfully most solid devs disagree with that also.

Oh stahp, have a laugh for once.

Guys, this is a cool and relaxed community. Understandably sometimes people are offended by something said or done, but lets keep it cool. People here want and do help unlike a lot of dev communities out there. Just let the little things go otherwise you'll never sleep. My 2 cents fwiw is be respectful and humble at all times.

If you need to relax and laugh go look at some of my code. The reason they allow me on this forum is because I make the rest of you look good :) If I say something is a bug you almost 100% sure that it is not, seriously, if I suggest there is a problem in Laravel it is not because I think I'm the worlds greatest developer, (might be the worst) it is an observation of my own workflow and code, not a sign of arrogance. Personally I think Laravel 5 is super solid, impressively so for just being released. I share with the intent of listening vs. being heard and am grateful for any feedback, good or bad. I think I'm improving and then I watch Jeff work through a video and I want to stop and go take up decoupage because I keep thinking I'll never get there and as long as I'm not there I keep learning, listening with humility.

They can take our annotations but they will never take our middleware!