On 12.11.2012 18:31, Katherine Marsden wrote:
On 11/11/2012 10:10 AM, Kristian Waagan wrote:
Hi Kathey,
Any specific reason why you're still using your own filter? If you
specify -1 the tool will use JQL (the JIRA query language) directly.
Just wondering if the tool is broken in some way and
On 11/11/2012 10:10 AM, Kristian Waagan wrote:
Hi Kathey,
Any specific reason why you're still using your own filter? If you
specify -1 the tool will use JQL (the JIRA query language) directly.
Just wondering if the tool is broken in some way and needs fixing. Or
maybe the documentation needs
On 25.10.2012 16:53, Rick Hillegas wrote:
On 10/24/12 4:13 PM, Katherine Marsden wrote:
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be
generated with 10.8.3 as the release version
On 11.11.2012 19:10, Kristian Waagan wrote:
On 01.11.2012 20:18, Katherine Marsden wrote:
On 10/26/2012 8:21 AM, Kim Haase wrote:
Hypothesizing that the reason the issues didn't make it into the
release notes was that they had been resolved but not closed, I've
closed those two issues. Maybe t
On 01.11.2012 20:18, Katherine Marsden wrote:
On 10/26/2012 8:21 AM, Kim Haase wrote:
Hypothesizing that the reason the issues didn't make it into the
release notes was that they had been resolved but not closed, I've
closed those two issues. Maybe that will help.
Hello Kim,
The reason for D
Oh, I should have read your note before I closed DERBY-4229! Thanks for
clearing that up, Kathey.
Kim
On 11/ 1/12 03:18 PM, Katherine Marsden wrote:
On 10/26/2012 8:21 AM, Kim Haase wrote:
Hypothesizing that the reason the issues didn't make it into the
release notes was that they had been re
On 10/26/2012 8:21 AM, Kim Haase wrote:
Hypothesizing that the reason the issues didn't make it into the
release notes was that they had been resolved but not closed, I've
closed those two issues. Maybe that will help.
Hello Kim,
The reason for DERBY-5925 was that my filter was not picking up
gt;>
>>> Both of them were also backported to releases farther back than 10.8 --
>>> but there was at least one more in that situation (DERBY-1721) that did
>>> make it in. A puzzle.
>>>
>>> Kim
>>>
>>> On 10/24/12 07:13 PM, Katherine
yptionKeyLength
>> connection attribute should be documented)
>>
>> Both of them were also backported to releases farther back than 10.8 --
>> but there was at least one more in that situation (DERBY-1721) that did
>> make it in. A puzzle.
>>
>> Kim
>>
&
herine Marsden wrote:
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be generated
with 10.8.3 as the release version.
Please review. I do have one question on the tool and generation. The
outpu
1721) that did
make it in. A puzzle.
Kim
On 10/24/12 07:13 PM, Katherine Marsden wrote:
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be generated
with 10.8.3 as the release version.
Please re
Dag Wanvik writes:
> On 25.10.2012 01:13, Katherine Marsden wrote:
>
> Note for DERBY-5564: The SQL state of the error returned from a
> lock timeout when the property "derby.locks.deadlockTrace=true" is
> set will return 40XL1 rather than 40XL2. 40XL1 is the documented
> SQL stat
On 25.10.2012 01:13, Katherine Marsden wrote:
> Note for DERBY-5564: The SQL state of the error returned from a lock
> timeout when the property "derby.locks.deadlockTrace=true" is set will
> return 40XL1 rather than 40XL2. 40XL1 is the documented SQL state for
> lock timeouts returned from Derby.
Hi Kathey,
The release notes look good to me. However, the summary sections for the
two detailed release notes are too long. In the releaseNote.html
template, the header comment for the summary section says that that
section is supposed to be one line. I have checked in a new version of
the t
On 10/24/12 4:13 PM, Katherine Marsden wrote:
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be
generated with 10.8.3 as the release version.
Please review. I do have one question on the
Hello Derby-dev,
Attached are the draft release notes for 10.8.3. They actually say
10.8.2.3 because until I merge the versions the tool cannot be generated
with 10.8.3 as the release version.
Please review. I do have one question on the tool and generation. The
output says one issue
16 matches
Mail list logo
