On Oct 2, 2004, at 6:22 PM, Aaron Mulder wrote:
Okay, I put in a Jira issue, checked in the fix, and resolved the
Jira issue. Is that the correct procedure?
Yep. Make sure you mark the issue as Affects M2 since this bug was in
the previous release, and fixed in M3 since it will be in the
On Sun, 3 Oct 2004, Dain Sundstrom wrote:
On Oct 2, 2004, at 6:22 PM, Aaron Mulder wrote:
Yep. Make sure you mark the issue as Affects M2 since this bug was in
the previous release, and fixed in M3 since it will be in the next
release. These version numbers drive our change log generation
On Sat, Oct 02, 2004 at 09:22:25PM -0400, Aaron Mulder wrote:
Okay, I put in a Jira issue, checked in the fix, and resolved the
Jira issue.
Hi Aaron,
I'm confident that GERONIMO-265 is caused by the same problem as
GERONIMO-349 so you (or David Jencks) can close that one, too. Thanks
On Oct 3, 2004, at 9:20 AM, Aaron Mulder wrote:
On Sun, 3 Oct 2004, Dain Sundstrom wrote:
On Oct 2, 2004, at 6:22 PM, Aaron Mulder wrote:
Yep. Make sure you mark the issue as Affects M2 since this bug was in
the previous release, and fixed in M3 since it will be in the next
release. These version
