The issue is only resolved at the moment... close it when it moves to
trunk.
But lets not argue over semantics in this time.
We are trying to use JIRA to track what needs to be done.
--jason
On Jul 20, 2006, at 2:52 AM, Jacek Laskowski wrote:
On 7/20/06, Prasad Kashyap (JIRA) <dev@geronimo.apache.org> wrote:
[ http://issues.apache.org/jira/browse/GERONIMO-1738?page=all ]
Prasad Kashyap resolved GERONIMO-1738.
--------------------------------------
Fix Version/s: 1.2
Resolution: Fixed
Let's mark this fixed. The patch has gone into the sandbox/
svkmerge/m2migration. The whole branch will be up for RTC review
anyway.
I disagree. Let's try to define when an issue is fixed. Let's face
what our end users face. If an end user consulted the issue today,
what would (s)he be left with? The answer is that (s)he will think
that the issue's fixed (I don't assume (s)he will eventually read the
description and draw his/her conclusion). This leads us to the
question whether it's really true. I believe, most if not all say that
it is not. Unless I'm mistaken in my thinking, I'd ask for re-opening
the issue and close it only when the patches have really been applied
to the trunk. As a matter of fact, we don't know yet when the svkmerge
branch will be merged so we don't really know what version the issue
is fixed in, do we?
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
