On Wed, Apr 1, 2009 at 6:09 AM, Lutz Jaenicke <l...@lutz-jaenicke.de> wrote: > > Probably you are not around long enough for the last (0.9.8) release :-) > In the past we tended to have the success reports sent to openssl-dev. > The problem with the success reports is that they are actually invalidated > with every new iteration so keeping those in the request tracker is not > the correct way. > I am considering on how to collect the success information which is > probably best handled with a "yes" or "no" (or the "yes: betaX") in a > spreadsheet. > Failures have to be looked into one by one and hence should go into > separate tickets in the request tracker.
You're right, I wasn't around for 0.9.8 beta. :) So, if I'm understanding correctly, I should send success reports to -dev, and failure reports to -bugs, along with... the reported (first) Target in the subject? There are two Target: lines: [...] Target: darwin64-x86_64-cc Compiler: Using built-in specs. Target: i686-apple-darwin9 [...] (The first is the argument to Configure, the second is the value of --target.) However, I'm thinking that if one beta passes, and then the next doesn't, that indicates a regression that needs to be examined -- so having the full reports available somewhere indexed would be a good thing? (For a spreadsheet, my schema would be to make multiple tabs -- the first for beta1, second for beta2, and so on. X axis (each column) would be the features that have been tested as working on the platform, Y axis (each row) would be a platform tested.) -Kyle H ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager majord...@openssl.org
