IMO, it is confusing and errorprone to introduce a new terminology
like GlassFish V1, V2, ... Vn when we already had a nomenclature in place
like: 9.0peur1_bxx and 9.1pe_bxx. For one thing, there is no point
in decorating GlassFish with V1s and V2s. Just call it GlassFish
and continue to use the target milestones (where a set of bugs are
fixed or a set of enhancements are integrated) to distinguish
the builds.
I hope at some point we distinguish between the GlassFish builds
and dependent product releases.
Simple procedure for GlassFish would be:
- Developers and bug committee decide the target milestone for a bug.
- IssueTracker reflects it.
- Users just look at the target milestone and download that build to
get the fix for the bug that they want fixed. (We can even think
of providing the link to the download location of the build corresponding
to the target milestone in the IssueTracker).
For GlassFish there should be one CVS location that it builds off,
and that happens to be the TRUNK, at the moment. GlassFish issues should be
tracked by IssueTracker alone.
Now, if there are product releases that have some fixes and not
other, they can be better tracked by other bug tracking systems that
have support for tracking multiple releases.
BTW, do we know how opensolaris does it?
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
>