db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Knut Anders Hatlen <Knut.Hat...@Sun.COM>
Subject Re: 10.4 Jira filters available
Date Tue, 01 Apr 2008 10:01:10 GMT
Dyre.Tjeldvoll@Sun.COM writes:

> Knut Anders Hatlen <Knut.Hatlen@Sun.COM> writes:
>
>> Dyre.Tjeldvoll@Sun.COM writes:
>>
>>> Hi,
>>>
>>> I have create two public Jira filter, 'Derby 10.4 Release Note' and
>>> 'Derby 10.4 Fixed Bugs' which I plan to use when generating the release
>>> notes. Links and a brief description can be found at
>>>
>>> http://wiki.apache.org/db-derby/DerbyTenFourRelease#head-5813efb99ae539012107121e6ad4005f77edc6a5
>>>
>>> Please let me know if you have comments or suggestions. 
>>
>> Hi Dyre,
>>
>> I'm wondering if the Fixed Bugs filter should be limited to those bugs
>> that were reported against released versions. For example, it now
>> reports bugs like these (not a complete list)
>>
>>  DERBY-3528 ReplicationSuite tests hang when running on jvm 1.5, jvm 1.4
>>  DERBY-3508 Log receiver thread fails with NPE at failover when master has died
>>  DERBY-3499 testStartStopManagementFromApplication junit test failure in nightly
test suite.
>>  DERBY-3493 stress.multi times out waiting on testers with blocked testers waiting
on the same statement
>>
>> all of which were bugs introduced and fixed on trunk, and never seen in
>> an official release. I'm not sure we want to list those bugs in the
>> release notes.
>
> I see your point. Here is a link to a modified query which only
> considers issues reported aginst a relased version:
>
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&type=1&type=4&type=5&pid=10594&component=11670&component=11406&component=12310670&component=12310194&component=11407&component=12312171&component=11409&component=11400&component=11690&component=11410&component=11709&component=12312050&component=11411&component=11415&component=11408&component=11412&component=11414&fixfor=12312540&fixfor=12313072&resolution=1&version=12312876&version=12312590&version=12312027&version=11187&version=12311953&version=12310615&version=10993&version=10991&version=10920&sorter/field=issuekey&sorter/order=DESC

Or perhaps two different queries would be better? For improvement and
wish, I think it makes sense to list all, since people who want to
improve something on trunk only often skip the affects version or set it
to the current trunk version. For bugs, the above query looks fine.

-- 
Knut Anders

Mime
View raw message