As mentioned earlier in my blog, we were able to take our bug from creating the ticket to submitting the patch. Due to the simplicity of our bug this whole process was relatively easy!
Submitting the ticket was as simple as filling out the form on the bug-tracker website. As we began reading TOS Chapter 7 regarding patches our next set of questions were answered. We knew how to fix the problem - writing the new code was very simple, but what were we supposed to submit to fix it? The answer was a patch, creating by diff-ing the original file with the corrected file. So we ran that simple command and named our file according to the best-practices guidelines found in our text book.
Now that we had created the patch we had to figure out Sugar's procedure for submitting them. After some research on the IRC and websites we found two methods. The first is to simply attach the patch to the bug ticket. The second was to submit the patch to the git server using the git send-email command. Since we weren't sure which was best, we did both! And then there was the waiting for a response.
I was extremely pleased to check my email this morning and find a chain of sugar emails related to our patch. More specifically, accepting it!
I also had a little problem with my Ubuntu system, requiring me to check-out the current version of sugar again and was pleasantly surprised to find our fix already in place! Success!
No comments:
Post a Comment