I believe so ony because I hadn't seen the last on your list.
The others are correct.
Carla
Eduardo Pelegri-Llopart wrote:
> IMHO, 9.0 pe v2 seems wrong. It seems to me it is either GF v2 or
> 9.1(pe)...
>
> Is this (conceptual) map incorrect?
>
> 9.0 <-> GF (v1)
> 9.0 UR1 <-> GF v1 UR1
> 9.1 (pe) <-> GF v2
> 9.{2/5} (pe) <-> GF v3
>
> - eduard/o
>
> Carla Mott wrote:
>
>> You're right. I think that issue tracker should use v1_ur1 and v2
>> bug track should stay as is and bug bridge should do the
>> mapping.
>> Carla
>>
>> Marina Vatkina wrote:
>>
>>> Hi Carla,
>>>
>>> Isn't 9.0pev2 even more confusing than 9.1pe? I thought that v2 is
>>> just v2 (as in GlassFish v2). With v1-UR1 in picture, I think we should
>>> either switch completely to vX or stay with 9.X, but not mix and match
>>> in between.
>>>
>>> My $.02.
>>> -marina
>>>
>>> Carla Mott wrote:
>>>
>>>> Not sure we can should bugtraq because it reflects our products.
>>>>
>>>> It would be nice to have the bug bridge do the mapping vs all the
>>>> developers and user of GlassFish. Most of the SQE folks know that
>>>> 9.1pe (bugtraq) == 9.0pev2 (isssuetracker) not sure if that is true
>>>> of the GlassFish community.
>>>>
>>>> my 2 cents
>>>> carla
>>>>
>>>> Deepa Singh wrote:
>>>>
>>>>> Hi Amy,
>>>>> I would like version in bugtraq and issuetracker to be same as I
>>>>> am using version field as-is from both places.
>>>>>
>>>>> Currently, bugtraq too has release for 9.1pe, 9.0peur1.
>>>>>
>>>>> If this were to change , i.e 9.1pe bugtraq == 9.0pev2
>>>>> isssuetracker, it would confuse our internal SQE team, and
>>>>> also,make bug management difficult.
>>>>>
>>>>> Can we change version in internal bugtraq as well?
>>>>> (We should all move to external issuetracker for PE, but there are
>>>>> some subcategories, for which there are no corresponding
>>>>> subcomponents in issuetracker for PE)
>>>>>
>>>>> Amy Roh wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> There has been some confusion regarding target milestone due to
>>>>>> the fact that we're using different names for GlassFish promoted
>>>>>> bundles and issue tracker target milestone.
>>>>>>
>>>>>> We're currently using 9.1pe... (sun internal) in issue tracker
>>>>>> but v2... for promoted bundles which is causing some confusion on
>>>>>> version names.
>>>>>>
>>>>>> I'm proposing we get rid of 9.1pe from issue tracker and to
>>>>>> change it to v2 so we're consistent with promoted builds. I'll
>>>>>> have to talk to Deepa regarding bugbridge impact but I'm assuming
>>>>>> it won't be a significant change but a simple mapping. Correct
>>>>>> me if I'm wrong.
>>>>>>
>>>>>> Any comments?
>>>>>>
>>>>>> Thanks,
>>>>>> Amy
>>>>>>
>>>>>> ---------------------------------------------------------------------
>>>>>>
>>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>>
>>>>>
>>>>> ---------------------------------------------------------------------
>>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
>> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: dev-help_at_glassfish.dev.java.net
>