Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of mcintyre.a@gmail.com designates
 66.249.92.173 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=oaOPRvrmtDBr2aYQjIH1W0hdwErgdCpV7we8wTKk4Lf24YavsAyPp8My97vaJYo60eDUkkQxByGyEvz0gdObgyk6kR/d6XQWdrzNkEcS8dXaB5KqR4fSbkweNleNzhxajP/LFsvnRKaoUo6prfGQDqaPRa5BPlDUp2AOiQd00G0=
Message-ID: <54ac72d70606132305j7720ae5bkddd6f4f697227981@mail.gmail.com>
Date: Tue, 13 Jun 2006 23:05:40 -0700
From: "Andrew McIntyre" <mcintyre.a@gmail.com>
To: derby-dev@db.apache.org
Subject: Re: [VOTE] 10.1.3.0 release
In-Reply-To: <1c5747850606132216q589d7010t4066a5c0285764ad@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <54ac72d70606131702t59fea234xe8795ccdfcac2a76@mail.gmail.com>
	 <1c5747850606132216q589d7010t4066a5c0285764ad@mail.gmail.com>

On 6/13/06, Mathias Herberts <mathias.herberts@gmail.com> wrote:
>
> Hi, I created issue DERBY-1373 on june second, I reported it as
> affecting 10.1.2.4 but I just checked your RC for 10.1.3.0 and the
> issue is still there.
>
> My report for the issue includes a (quick and dirty) fix for it so it
> might be included in 10.1.3.0 rather fast if someone reviews it.

Hi Mathias,

Thank you for reporting the issue and contributing the fix. Sorry, it
wasn't on my personal radar and wasn't marked Fix In 10.1.3.0 for JIRA
so I didn't take notice of it. There's a lot going on in the dev list,
so it helps to be loud about your contribution if it appears no one is
paying attention to it right away.

If there's a problem with this release candidate and we need to start
the voting over, we can probably get it into this release. Otherwise,
I'd like to continue the release vote on the proposed release
candidate as it is.

I've marked the issue with a Fix In of 10.2.0.0 so that it's
definitely on the radar for the next anticipated release.

andrew

p.s. maybe we should make a note on the 'tips for contributors' page
that people mark the Fix In (and not just the Affects field) for the
next appropriate release once you've contributed a fix?