Launch of laravel 4.3

In November, in sync with the Symfony release cycle.

I am not doubting you but where can i see the official information about it?

E.g. here (see title): https://twitter.com/taylorotwell/status/506224151670317056

It's basically 6 month cycle for launching every new versions of laravel . laravel 4.2 launched in may, laravel 4.3 is going to launch after 6 month in November and if there is laravel 4.4 then it will come in may.2015. you will be able to see it's beta version of 4.3 in the beginning of November on laravel official site. :)

No need to wait til Nov for beta: https://github.com/laravel/laravel/tree/develop - just download/unpack the zip, run "composer install" and there you are with your 4.3 WIP sandbox.

Yes.. of course not.. rspahni. i just mean that if you want to see it's beta version on laravel official sites then you have to wait for November.2014 . :)

With the impending launch of Laravel 4.3, my question is this, should I start using 4.3 on a new side project that will release first quarter of 2015 of start in 4.2 and upgrade?

I am at 2 minds to whether this is a good plan or just jumping the gun. Thoughts?

@mstrarkey I'd say it depends on whether you're using a lot of complex packages. I started to try and move over a project to 4.3 but put it on hold when I had trouble with Sentry.

I guess it's just pot luck if packages will still work with 4.3 or not. No harm in giving things a go though.

My opinion Nope, actually it's depend on your project how complex it is, 4.3 is still on cutting bleeding edge. it's good for practicing you skills and for contributors.. I'm also making an app which is going to release in 2015. and i'm working on laravel 4.2.

@mstrarkey Like everyone says it really depends on you and your project, however keep in mind that 4.3 is a big step up from 4.2 in terms of folder structure so if you're working on a large application this might be a pain (there's a service provider if you want to use the old file structure in 4.3 though)

I'm also working on an app that's going to release on 2015 and I'm using 4.3 mainly because:

• It's not going to be a super high traffic mega important app.
• I'm not using any Laravel specific packages.
• I want to learn about it before it's stable.

I don't see 4.3 changing too much until the final release, some people get scared by the word "beta" but instead try to use it as an opportunity to learn.

Hi all, I am going to start learning Lavarel from today, I see there will be a new release soon, how hard is it to update from 4.2 to 4.3 for example? Big Job? Thanks all

A good way to prepare for 4.3 is to start using namespaces and psr-4 for autoloading, if you have a look on how 4.3 app folder is structured and follow a similar approach for your namespaces then you will be able to migrate your app from 4.2 to 4.3 much more quickly.

Thanks for all your advise @pobble, @Rahul and @vengiss, I think because I am just starting to put code together, it might be a good time to start using 4.3, from my initial tests it works very well with what I am trying to do. The videos help me understand the new features and I guess by the time I get deep into the heavy lifting The 4.3 release will be ready. With regards to packages, I have decided at this point to work on the parts that do not rely on too many 3rd party packages and will stick with the laravel standards, swapping out if need be, I plan to use interface throughout as I am hoping the app will have a use for a lot of people.

I have been on 4.3 dev for a week or so with my fairly complex yet package-light project. No regrets so far (time will tell whether it was brave or stupid) but in any case, keep an eye on https://github.com/laravel/laravel/commits/develop (re structure, service providers, etc.; things that composer won't pick up) and https://github.com/laravel/framework/commits/master (so you anticipate what the next composer run might do to your project). I.e. follow Taylor & team closely in their footsteps.

i decided to start a new project in 4.3 as well today. so let's see, how it will play out.

with all new things, i think it would be quite painful to migrate it later from 4.2 to 4.3

Is it not called 5.0 now? I thought...

Yes it is: https://twitter.com/laravelphp/status/510098775553998848

Makes sense to call it 5.0. There are quite a few significant changes.