On May 10, 2010, at 11:36 AM, William A. Rowe Jr. wrote:
> On 5/10/2010 1:28 PM, Daniel Ruggeri wrote:
>> Hi, all.
>> I found this document today stating the following:
>>Each developer is responsible for notifying the mailing list and
>> adding an action item to STATUS when they have an idea
On 5/10/2010 1:28 PM, Daniel Ruggeri wrote:
> Hi, all.
> I found this document today stating the following:
> Each developer is responsible for notifying the mailing list and
> adding an action item to STATUS when they have an idea for a new feature
> or major change to propose for the product.
Hi, all.
I found this document today stating the following:
Each developer is responsible for notifying the mailing list and
adding an action item to STATUS when they have an idea for a new feature
or major change to propose for the product.
Since I am not a committer, how would I go about h
Sander/All;
Oh, I see. I guess my next question is how the issue fixed in trunk
gets proposed in the STATUS list. I submitted a patch that was added to
trunk, but am unsure if there is any additional action to take on my part.
P.S.
Also, is this information or process noted anywhere? I apolo
On Apr 20, 2010, at 12:41 PM, Daniel Ruggeri wrote:
> Hi all;
> I have a little confusion regarding the FixedInTrunk keyword when applied to
> a bug. What does it mean? My assumption is that it means that the code
> changes needed to fix the bug have been committed to the source repository
>
