[2.0] Roadmap

[davedevelopment]

@fabpot Is there any sort of roadmap for 2.0? Would love to help if I can :)

[gyndav]

👍

[jmontoyaa]

+1

[xmarcos]

👍

[zabusm]

+1

[fabpot]

I'm going to merge the 2.0-experimental branch into master as soon as 1.2 is released. Then, I will work on a roadmap. In the meantime, feel free to list the things you want to change/add/modify in Silex for 2.0.

[henrikbjorn]

I am also willing to lend a hand on a 2.0 release :)

[ghost]

👍 The only thing I'm interested in is Pimple 2 in Silex, @fabpot maybe if there is any changes to improve speed like you have done in pimple.

[davedevelopment]

Honestly can't think of any features. I think perhaps a cookbook about upgrading 1.x providers to 2.x providers would be good and I can contribute that.

[fabpot]

The 2.0-experimental branch has now been merged into master with support for Pimple 2.1.

[dominikzogg]

@fabpot is there a list with features you (we) d'like to have within silex 2?

[fabpot]

I think we don't really need any new "features". It's almost all about better documentation, and "enhancing" the current providers.

[ghost]

+1 to what fabpot said silex has all the features it needs ATM but better docs would be nice.

[dominikzogg]

@fabpot +1, are there any definitions for enhancements?

@ChrisRiddell I have nothing against better docs, but to know what have to be better would make it much easier to help.

[henrikbjorn]

Personally i think that we should look at extracting some of the core services from the Application class and into ServiceProviders.

[dominikzogg]

@henrikbjorn +1

@fabpot if you like what @henrikbjorn suggests, i would prepare the seperation of the dbal provider.

[stof]

@dominikzogg the DBAL services are already in a provider, not in the Application class

[dominikzogg]

@stof i totally missunderstood what @henrikbjorn, thx for telling me

[henrikbjorn]

@fabpot any news here, are we far off? I think a bunch of us are ready to do the bulk development work if we get a list or guidelines on where to head towards.

[ghost]

I'm also interested in what @henrikbjorn said.

[dominikzogg]

@ALL what do we have to do, that @fabpot could release v2?

[dominikzogg]

@ALL please add your allready ported providers to this page: https://github.com/silexphp/Silex/wiki/Third-Party-ServiceProviders-for-Silex-2.x

[simplyniceweb]

@fabpot when will be the official release of 2.0?

[fabpot]

Closing this issue. 2.0 is the master branch. I don't have anything left, so it's really up to anyone to propose nice things if any. I think we can mostly release it as is.

[dominikzogg]

@fabpot i would suggest to have symfony 2.7 components as minimal version, that its easy to update to symfony 3.0 components when they will be released. A silex 2.0 alpha tag would be nice.

[fabpot]

@dominikzogg Indeed, that's a good idea. Done for the 2.7 min dep.

[henrikbjorn]

I am still hopeing that the typehint for BootableServiceProvider is changed to pimple container instead of the application. Would make Cilex a lot better!

[fabpot]

@henrikbjorn It's not going to happen. The BootableServiceProvider interface is what ties Pimple to Silex. I want to be able to call mount for instance in a bootable service provider.

[dominikzogg]

@fabpot @henrikbjorn for example: https://github.com/silexphp/Silex-WebProfiler/blob/master/WebProfilerServiceProvider.php#L236 this line of code would make no sense within a pure commandline application

[henrikbjorn]

Well in that case it is clear that the ServiceProvider is centered around Silex. Anyways, dont really use Cilex.

[flip111]

Is there still something blocking a 2.0 release?

[dominikzogg]

@fabpot could we tag the 2.0-beta1?

[soullivaneuh]

@fabpot I'm also interested for 2.0 release date.

At least, can you confirm that 2.0 is feature frozen?

Thanks.

[dominikzogg]

it would be very cool, cause atm many providers need to support silex 1 and pimple 3

[fabpot]

We need to wait for Symfony 2.8/3.0 to stop deprecating/removing stuff first, and that happens very soon now.

[soullivaneuh]

@fabpot Thanks for the information about release plan.

Can you please confirm that Silex 2.0 is now features frozen?

[fabpot]

No, I don't, as I said before, we are waiting for 2.8/3.0 feature freeze first.

[soullivaneuh]

Oh ok, I misunderstood your sentence. Thanks for clarification. 👍

[dochne]

Is there any further information regarding a potential release date for 2.0 now Symfony 2.8/3.0 is released?

[lukaszwit]

Now when symfony 2.8/3.0 are released it there any estimation on Silex 2 release? I'd like to know if it's a matter of weeks or rather months? This would help me choosing right version for new projects.

[xiaohutai]

Looking forward to this 👍

[kabudu]

Any news on when Silex 2.0 will be released?

[dominikzogg]

i would prefere to release a beta first

[flip111]

It's been in beta pretty much ever since the last 1.* was tagged and master became 2.0 I'd prefer a stable 2.0 release

[sdmg15]

Why are pressing calm down .Don't put pressure to @fabpot .
For a saying " that will slowly will surely " Good night !

[Nayjest]

Is there any progress?

[jlchafardet]

yo! sorry for the bump, any progress here?

[ragboyjr]

@jlchafardet #1314 - We are just waiting on @fabpot to upload the 2.0 documentation to the website.

[jlchafardet]

oh tyvm @ragboyjr ill keep an eye! if 2.0 is turning stable, ill keep an eye on this