tactics for upgrading CodeIgniter?

[eluser]sneakyimp[/eluser]
I'm interested in upgrading my project from CodeIgniter 2.2.0 to the latest version, chiefly to address this bug:
https://github.com/EllisLab/CodeIgniter/issues/1890

The problem I have is that I do NOT want to overwrite files that I have changed. I can easily identify these files are ones that should NOT be overwritten:
ci/application/config/config.php
ci/application/config/database.php
ci/application/controllers/*.php
ci/application/core/*.php
ci/application/models/*.php
ci/application/views/*.php

I'm guessing that just unzipping the latest code igniter source download into my project folder is going to destroy config.php and database.php in the config folder at least. Can anyone recommend a good tactic for upgrading CodeIgniter?

[eluser]CroNiX[/eluser]
Sure, follow the upgrade guides: https://ellislab.com/codeigniter/user-gu...ading.html

[eluser]sneakyimp[/eluser]
[quote author="CroNiX" date="1406752023"]Sure, follow the upgrade guides: https://ellislab.com/codeigniter/user-gu...ading.html
[/quote]
The latest version listed in that list is the one I have, 2.2.0 and this is apparently the latest version. I guess I misread the post I had linked -- that bug still exists in version 2.2.0.

Where do I report a bug?

[eluser]CroNiX[/eluser]
Bugs are reported at the same CI repo on github, but it's already been reported as you linked to it Did you happen to read the thread in that report? Narf posted the 1 line fix.

CI 2.2.0 is the latest RELEASED version. CI 3 has been in development for some time now (also on github)

[eluser]sneakyimp[/eluser]
Thanks for detail. I wasn't aware that thread was an official CI page/resource/whatever. I'm not really interested in using a pre-release version of CI to be honest. I also find it puzzling that such a simple bug would not be fixed promptly.

[eluser]CroNiX[/eluser]
It was fixed (in CI3). They aren't doing any more development on 2.x except security updates (which is what 2.2.0 was). We're in the same boat and prohibited from using unreleased/beta code, so we haven't looked into CI3 much except to keep tabs on development, which has been going on for several years now with no tangible hint of a release date.