[MonoDevelop] about fixing bugs
ibboard at gmail.com
Mon Feb 20 08:22:30 UTC 2012
I think Bugzilla is only for assigning bugs to the team, not third parties.
What I did when I fixed bugs and added features (in the Novell days) was
fork on git hub, make a pull request referencing the ticket when I was done
and possibly put a comment I'm the ticket to say I was looking at it when I
At the end of the day, the team can only rely on their own staff not to
vanish, and one of the guys skool have to merge the change back anyway.
Hope that helps.
On Feb 20, 2012 8:09 AM, "Mansheng" <lightyang0 at gmail.com> wrote:
> Sorry, I didn't get it. Do you mean that I should submit a patch when I
> start to work on a bug? In that case, what should the patch contains? More
> importantly, how to know whether there is anyone working on that bug before
> I start?
> On 02/20/2012 02:54 PM, Sharique uddin Ahmed Farooqui wrote:
>> Hi Yang,
>> Submit a patch for that bug. This may not be the best way but it will
>> let others know that your are working on it.
>> Sharique uddin Ahmed Farooqui
>> "Peace" is the Ultimate desire of mankind.
>> On Mon, Feb 20, 2012 at 11:25 AM, Light Yang<lightyang0 at gmail.com>
>>> Hi all,
>>> How to start fixing bugs for monodevelop? I know bugs can be seen at
>>> bugzilla, but how do I get myself assigned for a bug or make sure no one
>>> else is currently working on a certain bug?
>>> Monodevelop-list mailing list
>>> Monodevelop-list at lists.ximian.**com <Monodevelop-list at lists.ximian.com>
> Monodevelop-list mailing list
> Monodevelop-list at lists.ximian.**com <Monodevelop-list at lists.ximian.com>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Monodevelop-list