river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Patricia Shanahan <p...@acm.org>
Subject Re: new release?
Date Fri, 12 Nov 2010 14:11:39 GMT
There are a couple of possible intermittent bugs I've identified through 
code inspection but that are not shown by any test. My original 
motivation for getting involved in pushing QA tests was the hope that 
the non-run would show these bugs.

One of them is very simple, and has a simple fix with low risk. I plan 
to post my analysis and a patch for it and ask for prior code review, as 
a substitute for a regression test.

The other is much more complicated, and any fix would have substantial 
risk. I'm in the process of seeing if any of the newly activated QA 
tests hit that area. Determining if it is a real bug, and if so fixing 
it, is a longer term project and probably should not delay the next release.

My overall view is that the current trunk build is better quality than 
the last release, and should be offered to users. Users can make their 
own choices about whether to move to the latest build.


Tom Hobbs wrote:
> What else is would be included in this release?
> Is it mostly bug fixes which make the QA tests pass or anything extra?
>  I remember that there is a tool or something clever we can do with
> Jira to generate some release notes.  Can anyone remember what it was?
> I like the idea of releasing often.
> On Fri, Nov 12, 2010 at 11:11 AM, Sim IJskes - QCG <sim@qcg.nl> wrote:
>> On 12-11-10 12:02, Peter Firmstone wrote:
>>> Sim IJskes - QCG wrote:
>>>> Now that we have the QA testing working, a very important step, should
>>>> we go for a release?
>>>> My personal feelings are: It is really a big step, which merits a
>>>> release on its own.
>>>> Gr. Sim
>>> Yes definitely soon, there are still two failing qa and one jtreg test
>>> I'd like to look at, if I get some time over the weekend, I'll
>>> investigate setting up the KDC also, then we should release.
>> Shall we document that we couldn't verify kerberos, and still do a release?
>>> Can we blow away our old web page yet? The old apache web page doesn't
>>> mention our previous release news for 2.1.2, only the vote request, I
>>> edited it on confluence, but it never made it to the main site.
>> I will come back on that.
>> Gr. Sim
>> --
>> QCG, Software voor het MKB, 071-5890970, http://www.qcg.nl
>> Quality Consultancy Group b.v., Leiderdorp, Kvk Den Haag: 28088397

View raw message