Welcome Guest, Not a member yet? Register   Sign In
CI Development Cycle
#1

[eluser]Kyle Johnson[/eluser]
So I've been monitoring some of the changes to the CodeIgniter git repository, but I'm noticing that there are commits that don't end up making it into the master or stable branches. Even though they are in the develop branch, or the feature/db_forge branch.

I'm curious how long it takes for a merge to make it up to the master branch for an official release. Obviously some make it up before others, but something like (https://github.com/EllisLab/CodeIgniter/pull/719) which was committed 8 months ago still hasn't made it through.

Would love to see that one be officially released, but understand that there may be concerns with it (but those seem to have been addressed in the pull request). The guidelines on the Github page state, "If nobody has a problem with the change then it will be merged into develop and will be part of the next release." So it made it into the develop branch 8 months ago, but hasn't made it to a stable branch yet.

Can anyone enlighten me?

#2

[eluser]CroNiX[/eluser]
There's only a few people who can really answer that, and they aren't on the forums too often.
#3

[eluser]Aken[/eluser]
To my knowledge, there are no plans for any additional features to be added to the 2.x branch. Only bug and security fixes will be pushed, with 3.0 being the next major release.

The develop branch is pretty stable as-is if you want to use it (at your own risk, naturally). Otherwise you can always patch your own code with any additions you'd like to make in the meantime.
#4

[eluser]Kyle Johnson[/eluser]
Thank you both.

That's kind of what I was thinking, no new features in the 2.1 branch, no matter how awesome they might be. Smile

I guess I can probably vote for features on user voice.
#5

[eluser]Aken[/eluser]
They've discontinued the use of UserVoice as well. If you have feature ideas, submit them as Issues on GitHub, or add your opinion and encouragement to existing ideas. Participation through GitHub is the best way to contribute to CI being updated and released, even if it's providing feedback.

https://github.com/EllisLab/CodeIgniter

Oh, and if something has already been committed to 3.0, it will be a feature. Don't really need to vote on it when it has already been implemented. Smile




Theme © iAndrew 2016 - Forum software by © MyBB