Quote:
Originally Posted by DrChiper
What I miss in the above discussions is how to guarantee that the community code changes find their way back in the main branch of of the source code of the original developer/maintainer. When that developer/maintainer has already made changes without some official release yet, how can we make sure the temporary community fixes do not get lost or even break existing code?  |
I don't think this is a very common situation. Community code is a very strange ocurrence, usually only the maintainer attaches a beta to a message.