Applying a patch

[aostad]

I have installed the package with all fixes a month ago. I'm just wondering if there is a way to apply a patch which fixes a specific issue instead of re-installing the package with all fixes.

Actually installing the whole package is not easy, as I have some customization in the Testlink and a merging will be needed if I re-install the package. I just need changes in the code for fixing a specific issue.

[fman]

first thing is :
if you have done changes, what are this changes ? why this changed can not be provided to community ?
This way you will have better chances.

each commit on gitorious has detail of all changes files and the changes done, but we work in the best way our time allow us, this does not means
that some other code on a previous commit CAN BE IGNORED .
At least this is all I can say (may be other have a better solution that can be shared)

[aostad]

The customization that I've made is just useful for the company I work for. They are regular stuff like adding different test status, renaming some labels, using company log, integrated with a new issue tracking system and so on. I have already posted these changes since I joined the community. I'm sure many users of Testlink do the same thing and customize it for their company.

I remember you guys used to provide a fix to the reporter of issue, so he/she could try and verify it locally. It's good to exercise a fix in the environment that it's been detected.

My two cents: That would be nice that Testlink admin/developers use the way that they used to verify a fix by sending it to the bug reporter. That way, users can enjoy fixes and don't need to wait for a long time until next official version. Nobody can afford to mess with a production server to replace the Testlink with a bug fixed version that is changing every couple days. But minor changes can be done as the user have a better control of it.

[fman]

IMHO you have not fully understand the process we have using to provide fixes.
All fixes are available via git commits, this means that people can make changes to his/her installation.
I'm user of mantis for at least 9 years and I've never thinked about asking them to provide an special fix for my requests.
If they fixed and provide commit I got for the code and try to apply it.
To do this a minimal knowledge of PHP is needed.
I repeat We are providing what you ask for: you have the fix you need for each issue that people has reported.

If you have only done configuration changes to your installation, i can not understand how to install a new patched version can ruin your work.
The head of our branch 1.9 is as good or as bad as 1.9.5 will be.

In order to provide any other kind of service, we will be forced to ask for support for our work.

[Amaradana]

@aostad : I use for such customization this way, as in one off the previous company when am working, they do had similar kind of customization and i have done that. In such case i used to maintain 2 local copies of TL instamce One, back up of current production instance and the second is for all the R&D like add bug fixes i need or any changes that am trying to achieve if everything is fine, then i would move that code to production. This is how i followed and i always ask time if they need any customization

Not sure if that helps you, just shared how i used to track..

[aostad]

Thanks for suggestion.