Hi there,
Recently we went about researching and looking for a PHP framework that fitted in with our desired development principles and coding standards and really liked the look of FuelPHP and as such developed an internal utility using FuelPHP v1.2, and it seemed to perform the required job perfectly and we really liked the principles behind FuelPHP's coding and framework.
We are about to embark on the development of a large project of building a proprietary system, but are in a bit of a dilemma as we can see that the core development of the framework has now shifted over to v2.0 (or at least core concentration from what we can gather).
With this in mind I was hoping for a frank and honest reply from the FuelPHP dev team on the sort of timescales envisaged for v2.0 of the framework, because I know the code is already available in it's current state to play with. But what we are not sure of is whetrher the feature complete vision of 2.0 will be available in mere months or more likely in over a years time, as this may effect the choice of FuelPHP as the framework of choice.
In essence we don't want to build the system on a framework and it's current core classes in a way that will be deemed out of date by the time the system comes to launch, and thus in essence have to rely on a legacy mode when upgrading.
We understand the reasons for the changes in 2.0, and are willing to start development with it, but are also weary on what changes may occur leading to the final release of v2.0, so if this could be clarified or expanded upon it would be helpful in allowing us to decide how to progress.
Best wishes,
Alex
I was thinking something similar. I've knocked up a small personal site on my local network to try Fuelphp using version 1.2 which I liked. I'm about to start a larger public facing site that will host a lot of user driven content, some social networking aspects, queries crossing databases, user access levels in both frontend and administration pages etc. I don't want to start that in Fuelphp 1.3 knowing 2.0 is on the horizon, but I'm reluctant to start it in Fuelphp 2.0 beta if the finished 2.0 is a long way off and will end up bearing little resemblence to the current 2.0 beta
There isn't a clear timeline, as we are not a company sponsored team, we have to do this in our free time. And there are times when we don't have any.
I think it will be reasonable to expect a least a 2.0 RC towards the end of the year. The framework kernel is ready and tested, but not documented yet. Jelmer already has converted all his apps to 2.0, but uses external solutions for the non-kernel parts (like ORM, images, session, etc).
You can expect the API to remain virtually unchanged to what it is today. Next step is to work on the Core (which is a separate package in 2.0), adding the functionality that we have today in terms of supporting classes. Some we will port, some will need to be rewritten, some we're not going to convert as there are better solutions available (for example for the image class).
We will provide a 'legacy' translation layer for those wanting to migrate an existing 1.x application, as the API is quite different then it is today.
I currently develop my applications on 1.4/develop. It's proven, stable and fast. When 2.0 is out, I will see for each of the applications if there is a need to port them to 2.0. I'm pretty sure that for a lot of them, there won't be an immediate need. An even after 2.0 is released, there will be (maintenance) support on the latest 1.x version.
Hi Harro,
Thank you for taking the time to respond to my query, I fully appreciate the fact that the FuelPHP team are not a company sponsored team and as such development is completed in free time, and I can't emphasise enough that the work you guys are going is much appreciated by the whole FuelPHP community.
That's why we are keen to adopt the framework and it's principles in our core development of our next major project, but because of the impending release of 2.0 which uses different principles we do not wish to rely on a 'legacy' layer in order to use the new aspects of 2.0.
With this in mind, based on your current core classes, have you got an idea on what your priorities are in the sense of what core classes will be developed first? As it could help us decide on whether or not to begin work with 2.0 and use the core classes as they arrive and as we need to use them.
Once again, appreciate your prompt response.
Best wishes,
Alex
We need to work on a detailed roadmap, and assign tasks. This will also allow us to be more specific about an RC date. There are some core classes that will have priority over others, such as Session.
Jelmer's been very busy the last month due to local elections (he's involved in politics), Frank's been on holiday. I'm planning a team meeting to have these things sorted out, so we'll be able to have a clearer view on the tasks ahead.
Harro, thanks again for your prompt responses.
We are looking at timescales of development of our system starting in early November spanning through until April next year potentially.
So if you are planning to roadmap aspects before this then it will most likely give us ground to make a decision on how to move forward.
Will you be posting this roadmap to a public domain? Or just general details via a blog post?
Donate
