Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: pass (nike.apache.org: domain of m.v.lunteren@gmail.com
 designates 74.125.83.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=toUUiW39PFnOumZypg+zabUf1GmTJk+62Wp7KLOOcGmYOpPg/0OpemXtWy1va4IFIP
         1SO6o9ip2VZ1J3zVfVtLgF2FK8K8RE1nGIiK/7co06SYyQ5fdQIpMM92m0OWvAUpiy6y
         tWX4QD0+opQsMgWugocLV5JQ+BTdQSKG5eLO0=
MIME-Version: 1.0
In-Reply-To: <x6tybj6vru.fsf@oracle.com>
References: <BANLkTikAA06g79sgG2FykjERVWsY95sQEw@mail.gmail.com>
	<4DFF9E3A.7030202@oracle.com>
	<BANLkTi=1WpzFGpPTpDncvFw6zMGkcNUeBw@mail.gmail.com>
	<4E00924A.1030508@oracle.com>
	<4E009A6A.1060104@oracle.com>
	<4E00A1B6.1070204@oracle.com>
	<x6tybj6vru.fsf@oracle.com>
Date: Tue, 21 Jun 2011 10:26:13 -0700
Message-ID: <BANLkTi=rxtm_aa7r3HrtFHv-eQTNbjqfmg@mail.gmail.com>
Subject: Re: can someone add 10.8.2.0
From: Myrna van Lunteren <m.v.lunteren@gmail.com>
To: derby-dev@db.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Jun 21, 2011 at 8:37 AM, Knut Anders Hatlen
<knut.hatlen@oracle.com> wrote:
> Rick Hillegas <rick.hillegas@oracle.com> writes:
>
>> On 6/21/11 6:19 AM, Kristian Waagan wrote:
>>> On 21.06.11 14:44, Rick Hillegas wrote:
>>>> On 6/20/11 1:04 PM, Myrna van Lunteren wrote:
>>>>> On Mon, Jun 20, 2011 at 12:23 PM, Rick Hillegas
>>>>> <rick.hillegas@oracle.com> wrote:
>>>>>> On 6/20/11 11:52 AM, Myrna van Lunteren wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> Can one of those with sufficient karma add 10.8.2.0 to the list of
>>>>>>> releases in JIRA?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Myrna
>>>>>>>
>>>>>> Hi Myrna,
>>>>>>
>>>>>> What would the new release number be used for? Is there any difference
>>>>>> between 10.8.2.0 and the current head-of-branch marker (10.8.1.4)?
>>>>>>
>>>>>> Thanks,
>>>>>> -Rick
>>>>>>
>>>>> This would be for the bug fix release planned for September. We
>>>>> typically increase the 3rd digit for those, I thought.
>>>>> Right now, I only wanted to assign placeholder task for it...there's
>>>>> no difference yet between top of the 10.8 branch.
>>>>>
>>>>> D'you think we should hold off creating this version # because it
>>>>> might be confusing?
>>>> People may be a little puzzled about when to use 10.8.1.4 vs. when to
>>>> use 10.8.2.0, particularly for the "fixed in" field. My inclination
>>>> would be to not create a 10.8.2.0 release id at this time. Instead, you
>>>> can rename 10.8.1.4 to be 10.8.2.0 just before you create the first RC.
>>>
>>> +1 from a bug reporting perspective, especially since JIRA provides
>>> a way to easily handle this (rename/merge).
>>> The downside may be that it is harder to mark something as "due" for
>>> the future maintenance release, but I don't think we have been doing
>>> that a lot (?).
>>>
>>> Although not a big deal, maybe filters are affected too?
>>> (i.e. the RM must currently use version 10.8.1.4, but when 10.8.2.0
>>> is created the filters must be updated?)
>> I'm comfortable with draft release notes which say 10.8.1.4. The
>> switch to 10.8.2.0 can happen just before the RC is built.
>
> I've now removed the 10.8.2.0 version. Myrna, I think you have the
> permissions required to add/remove versions yourself since your JIRA
> user is member of the derby-administrators group. You should have an
> "Administration" drop-down menu where you can choose "Project: Derby"
> and then "Manage versions" when you get to the project page.
>
> --
> Knut Anders
>

Thank you all for your help and input!

Myrna