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 for a
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 and the fix will be available
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.
apologize for
polluting the general mailing list with basic process questions.
--
Daniel Ruggeri
Sander Temme wrote:
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
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 and the fix will be available in the next stable release
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
