dev@glassfish.java.net

another query that might need folks to evaluate

From: vince kraemer <Vince.Kraemer_at_Sun.COM>
Date: Fri, 26 May 2006 11:02:00 -0700

This query checks to see which fixes were made AFTER 30 march 2006 and
have been marked with an FCS branch build in the Target Milestone.

https://glassfish.dev.java.net/issues/buglist.cgi?Submit+query=Submit+query&component=glassfish&version=9.0pe&target_milestone=9.0pe_b43&target_milestone=9.0pe_b44&target_milestone=9.0pe_b45&target_milestone=9.0pe_b46&target_milestone=9.0pe_b47&target_milestone=9.0pe_b48&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfield=resolution&chfieldfrom=2006-03-30&chfieldto=Now&chfieldvalue=FIXED&short_desc=&short_desc_type=substring&long_desc=&long_desc_type=substring&issue_file_loc=&issue_file_loc_type=substring&status_whiteboard=&status_whiteboard_type=substring&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&newqueryname=&order=Reuse+same+sort+as+last+time

I would like to PROPOSE that we flag fixes in this query as:

V2-TRUNK (if the fix is in the V2 trunk) or NOT-V2-TRUNK (not in the
trunk) [in the Status whiteboard field]

For example: https://glassfish.dev.java.net/issues/show_bug.cgi?id=520

would be flagged V2-TRUNK.

As an aside: folks who use a method like Marina's (see issue 520 for an
example)to document their fixes will have a very easy time with task.
Folks that don't, may have to do a bit more digging in fisheye...

vbk