04-14-2015, 12:53 AM
Hi
At the moment we have just 1 base repository: bcit-ci/CodeIgniter which contains all the code issues / pull requests / commits and etc.
From many others git based projects we can think for splitting a little bit the framework into components/drivers and to keep the current bcit-ci/Codeingiter as Framework repository.
There are many things which are or can be stand alone as Session / Cache / Database / Logs / CORE..
Those things can be in a separate repositories for each component.
And at the original bcit-ci/CodeIgniter we can keep the current complete variant of the framework.
Its not going to be hard of support. The only difference will be merging each component after a commit is confirmed as stable and tested inside the main repo.
How ever the current way is not wrong either so we can leave it as it is.
I wont start pull as this is more CI council decision..
What do you think about this ?
At the moment we have just 1 base repository: bcit-ci/CodeIgniter which contains all the code issues / pull requests / commits and etc.
From many others git based projects we can think for splitting a little bit the framework into components/drivers and to keep the current bcit-ci/Codeingiter as Framework repository.
There are many things which are or can be stand alone as Session / Cache / Database / Logs / CORE..
Those things can be in a separate repositories for each component.
And at the original bcit-ci/CodeIgniter we can keep the current complete variant of the framework.
Its not going to be hard of support. The only difference will be merging each component after a commit is confirmed as stable and tested inside the main repo.
How ever the current way is not wrong either so we can leave it as it is.
I wont start pull as this is more CI council decision..
What do you think about this ?
Best VPS Hosting : Digital Ocean