Patches
Patches are a way to distribute changes to files. In the context of ProjectPier, it means that patches usually describe changes to code. In fact, patches describe the changes between a before and after state. That means that if you have ProjectPier in the before state you can arrive at the after state by simply applying the patch.
We use patches for content control even though ProjectPier is distributed via SVN. This is because patches provide a great deal of control and convenience; they are small, plain-text and can be sent via e-mail; they are focussed on a change and therefore easily read and judged.
This also means that a SVN-account is not required to supply patches; anyone with a ProjectPier.org account can go to the issues queue to upload a patch. The tips for contributing apply to core as well as contributed modules.
Patches serve a second purpose; some modules require changes to ProjectPier core files. Some module authors provide modified modules, others give you patches to do it yourself. It is recommended to use already patched files provided by the module author. When these can't be used or are not available, use patches, but exercise caution.
Warning: Patching is something that should never be done on your production site unless you have sufficient backup and testing performed. While patching itself is relatively easy, understanding the implications of a patch is not. Patching your system can lead to loss of data and/or site instabilities
Hi,
Would it be possible to have a patch-list? This way we don't have to read every issue, but just read the patchlist. I think it would be a good idea to post a link to the issue in the patchlist and a link to the patch in the issue.
For example I'm searching for the patch about timetracking...but I can't find it. In a patchlist, I would have found I very easy ;-)
Is this what you're looking for? http://www.projectpier.org/project/issues/ProjectPier?states=8%2C13%2C14
If that is not what you're looking for, can you please point out an example from a different project that provides this?
Also, I should point out that the patch que is mostly for testers/developers and should not be applied to production environments unless you are aware of the ramifications (this will also affect your upgrade options)
Hi,
Yes, it is what I'm looking for, only I didn't find it earlier (was very close although ;-) ). Are all the developers consequently in changing the status?
I know it is just for testing.
I am not sure what you mean by your question. All registered users can contribute patches and also have the ability to change the status of an issue (which can include marking it as having a patch)