Based on this response, I would like to reiterate my request for a value
of the Target Milestone that represents the real commitment to
implement/fix an issue by the time V3 ships.
This response sounds like a resounding "maybe".
If we cannot add a value to the Target Module field that implies...
sometime in the future... is there a combination of priority and Target
Milestone that we can use to clearly identify what issues that have been
filed are being addressed and which might be addressed and which won't
be addressed in the V3 release?
Assigned engineers should be able to set their issues to clearly
communicate their plan for v3 development work.
Thanks,
vbk
Hong Zhang wrote:
> Hi, Vince
> (I can only speak for the deployment area).
> As we still have a pretty long to-do list for re-implementing v2
> equivalent features and implementing new v3 features, it's hard to
> know at this point whether we would have time to address the open
> enhancements (if they are still applicable). We will keep the
> enhancement list in mind when we are implementing the features and we
> will examine the list more carefully once we finish implementing the
> main pieces.
> Thanks for your understanding.
>
> - Hong
>
>>
>>
>> I just did a query on enhancements that are targeted for v3 in the
>> issue tracker:
>> https://glassfish.dev.java.net/issues/buglist.cgi?Submit+query=Submit+query&issue_type=ENHANCEMENT&component=glassfish&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&target_milestone=V3&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&short_desc=&short_desc_type=fulltext&long_desc=&long_desc_type=fulltext&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time
>>
>>
>> The list has about 90 entries.
>>
>> Are all of those enhancements really going to be addressed in V3?
>>
>> I am particularly interested in these:
>>
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=583
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=670
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=1048
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=3386
>> https://glassfish.dev.java.net/issues/show_bug.cgi?id=4451
>>
>> If an enhancement is not going to get addressed in V3, can we create
>> a value for target milestone that provides a hint about that?
>>
>> Thanks,
>> vbk
>>
>> ---------------------------------------------------------------------
>> 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
>