db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rick Hillegas <rick.hille...@oracle.com>
Subject Re: Revive or retire http://wiki.apache.org/db-derby/PlatformTestsDerby?
Date Tue, 19 Oct 2010 13:27:16 GMT
Knut Anders Hatlen wrote:
> Kristian Waagan <kristian.waagan@oracle.com> writes:
>>  Hi,
>> I stumbled across [1] when looking for something on the wiki.
> There's also a link to it from the front page, in the "Nice to know..."
> section.
>> It lists the various Java platforms Derby has been tested
>> on. Unfortunately, it hasn't been updated since 2008-04-25.
>> Is it useful enough to revive, or should we simply remove the page?
>> If keeping, should we simplify it by specifying major.minor version only?
> I can see the value of this page. If someone volunteers to update it,
> that is. Simplifying the list of versions sounds fine, as that would
> make both reading and maintaining the page easier. We usually don't
> change the supported JDBC levels in maintenance releases, so we wouldn't
> lose information that way. And if we ever do that, we could just add a
> note about that specific version.
This page might be useful if it were revamped to be our master release 
wiki page. The pointers in the "Release" column of the first table would 
be useful to me if they pointed further into the release wiki, rather 
than at information which lives prominently on the master download page. 
By following links in the "Release" column, the reader would get to the 
actual testing specifics for each release:




Bear in mind that I'm in the process of REDUCING the number of tasks 
which the release manager has to perform. Perhaps we can organize the 
platform testing results better so that we don't need to summarize 
results on this page.

My $0.02,

>> Finally, I'm not sure if the "Tested Combinations" section gives much
>> value. I can't read out for which releases the different combinations
>> were tested. Would it be better to include links to the release
>> platform testing pages instead, for instance [2]?
> I agree. Keeping track of all tested combinations for all versions in a
> single table will become messy. And it sounds unnecessary to duplicate
> the information that's already available from the release platform
> testing pages, so links would be fine.

View raw message