You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by Knut Anders Hatlen <Kn...@Sun.COM> on 2008/04/01 09:24:38 UTC
Re: 10.4 Jira filters available
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.
--
Knut Anders
Re: 10.4 Jira filters available
Posted by Dy...@Sun.COM.
Rick Hillegas <Ri...@Sun.COM> writes:
> Dyre Tjeldvoll wrote:
>> Knut Anders Hatlen wrote:
>>
>>> 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.
>>
>> Probably. But I don't know how amenable the release note utility is
>> to taking more than one file as input. Since the input is in the
>> form of an xml-file, you can't just concatenate the results from two
>> queries and feed it to the release note generator. Maybe it would be
>> possible to merge the xml-files by hand, but I have not looked at
>> the format so I don't know how easy that would be...
>>
>>
>> Dyre
>>
> I'll bet that we could tweak this code to wrap an XmlVTI around each
> of the input files. The two VTIs could then be unioned and sorted by
> release id. The release note generator could then walk the merged
> ResultSet and throw away duplicate keys.
I have mofified the 'Derby 10.4 Fixed Bugs' filter to only select issues
of type 'Bug'.
I created another filter 'Derby 10.4 Improvements':
https://issues.apache.org/jira/secure/IssueNavigator.jspa?mode=hide&requestId=12312524
It lists 45 issues, but I feel that most of them do not belong in the
release notes. There are a couple of exceptions, e.g.
https://issues.apache.org/jira/browse/DERBY-2887
https://issues.apache.org/jira/browse/DERBY-2653
https://issues.apache.org/jira/browse/DERBY-1931
--
dt
Re: 10.4 Jira filters available
Posted by Rick Hillegas <Ri...@Sun.COM>.
Dyre Tjeldvoll wrote:
> Knut Anders Hatlen wrote:
>
>> 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.
>
> Probably. But I don't know how amenable the release note utility is to
> taking more than one file as input. Since the input is in the form of
> an xml-file, you can't just concatenate the results from two queries
> and feed it to the release note generator. Maybe it would be possible
> to merge the xml-files by hand, but I have not looked at the format so
> I don't know how easy that would be...
>
>
> Dyre
>
I'll bet that we could tweak this code to wrap an XmlVTI around each of
the input files. The two VTIs could then be unioned and sorted by
release id. The release note generator could then walk the merged
ResultSet and throw away duplicate keys.
Regards,
-Rick
Re: 10.4 Jira filters available
Posted by Dyre Tjeldvoll <Dy...@Sun.COM>.
Knut Anders Hatlen wrote:
> 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.
Probably. But I don't know how amenable the release note utility is to
taking more than one file as input. Since the input is in the form of an
xml-file, you can't just concatenate the results from two queries and
feed it to the release note generator. Maybe it would be possible to
merge the xml-files by hand, but I have not looked at the format so I
don't know how easy that would be...
Dyre
Re: 10.4 Jira filters available
Posted by Knut Anders Hatlen <Kn...@Sun.COM>.
Dyre.Tjeldvoll@Sun.COM writes:
> Knut Anders Hatlen <Kn...@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
Re: 10.4 Jira filters available
Posted by Dy...@Sun.COM.
Knut Anders Hatlen <Kn...@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
--
dt