RTEMS Patches (was Re: FTP client API)

[chrisj at rtems.org (Chris Johns)]

On 23/04/2010 12:50 AM, Arnout Vandecappelle wrote:
>
>   PS It's not entirely clear to me now if patches for new features should be
> sent on the mailing list or submitted on bugzilla or both?
>

I am sorry my mailing list post may appear a little confusing.

RTEMS is relaxed about this. We do not define a specific procedure that 
must be followed. This allows us all some slack which we can work with. 
You can decide on a suitable way to interact and get changes into RTEMS 
based on the type of issue, size, and complexity.

I see this is different to the information currently in the Wiki under 
Submitting Patches. Maybe the Wiki needs to be updated to add using 
Bugzilla.

My take on this topic follows.

Bugzilla provides a state driven database of open tickets. Changes 
handled this way can be searched, linked, and managed openly with a full 
history of the discussions attached to the ticket. The ticket is always 
present so the history is always available. If you find a bug or suspect 
a bug please add it. It is simple to say, not a problem, duplicate, or 
fixed and to close it. For patches, if you are working on a change that 
is big, or has a long life cycle then a ticket maybe be better.

Patches to the mailing list are always welcome but can be lost or 
maintainers may think someone else is handling it. I know I need to keep 
a thread around in case I have missed a piece plus it can become 
confusing knowing which patch or patch set is correct.

I hope this helps.

Chris