I work in a software company where we have many projects for different clients.
We are facing the problem that some of the software is built on an old framework (Rails 3.2). Now, the customer has paid for making some new features to the project. The question arrises on upgrading the framework (at least to Rails 4.2, last version is 5), or just work with the software the customer has paid for. Our options (how I see it) are:
- Try to convince the customer to paid for a framework update. It's pretty hard since they won't see any change, but it's easier to maintain. If the customer doesn't want to pay, this means to work with the old framework.
- Update the framework and count it as a mandatory fee for "touching" the project.
This is important not only for this project, but a guideline for future projects. Should we allow to have outdated projects? This is quite annoying for developers. On the other hand, update the framework can be pricy as well.