Redmine

Chris Grieger wrote:

I'm new here and looked through some of the Issues/Defects which i could fix.

Great, thanks... Welcome to the club! Happy mining... :)

Chris Grieger wrote:

Is it allowed to post a Patch to an issue which has already been assigned to someone else?

Yes, not a problem but some communication can prevent double work. I'd post an issue-journal asking the current status from the assignee to at least make sure he/she hasn't completed the implementation for let's say 90%.

Some general info can be found at the following wiki-pages:

• contribute
• submissions

Kind regards,

Mischa.

Thank you for your reply.

There are a lot of entries in the patch tracker what has to be done with those tickets? Is it enough to check if they are working in the current trunk?

Regards,

Chris

Chris Grieger wrote:

There are a lot of entries in the patch tracker what has to be done with those tickets? Is it enough to check if they are working in the current trunk?

A lot of patches are outdated so they don't apply cleanly to the latest code. You can try to fix / update the patches so they can apply cleanly to the latest code.

Regards,

Mischa.

Chris Grieger wrote:

I'm new here and looked through some of the Issues/Defects which i could fix. Is it allowed to post a Patch to an issue which has already been assigned to someone else?

Welcome to the community. Yes, please post patches or review any of them that are already attached. If you like a patch that was submitted already, post a comment saying that you like it. If you decide to submit a new patch, write a comment explaining why. It can be something basic like "Added a test for an edge case for Patch12". When I'm reviewing an issue, I'll look at most of the patches and pick the best parts out of each one to submit.

Eric