I too was under the impression that "Fix version" indicates what versions the fix should go into.  If "Fix version" is not to be used for this purpose, then we will need an alternative mechanism to identify JIRAs that we should target to resolve in any particular release.

Thanks,
Vamsi

On 10/11/06, Aaron Mulder <[EMAIL PROTECTED]> wrote:
How else can we track what versions we believe it should be fixed in?
I don't know how else I'd find issues to fix in 1.1.2 out of the 500+
open issues.

Thanks,
     Aaorn

On 10/10/06, Jason Dillon < [EMAIL PROTECTED]> wrote:
> Its not a good idea to set the fix for version when creating an
> issue.  This should be set when closing the issue.
>
> --jason
>
>
> On Oct 10, 2006, at 1:17 PM, Aaron Mulder (JIRA) wrote:
>
> > Remove console JARs from WEB-INF/lib
> > ------------------------------------
> >
> >                  Key: GERONIMO-2482
> >                  URL: http://issues.apache.org/jira/browse/
> > GERONIMO-2482
> >              Project: Geronimo
> >           Issue Type: Bug
> >       Security Level: public (Regular issues)
> >           Components: console
> >     Affects Versions: 1.1.1
> >             Reporter: Aaron Mulder
> >              Fix For: 1.1.2, 1.2
> >
> >
> > It's unnecessarily hard to build console extension plugins because
> > the car-maven-plugin can't access JARs in a WEB-INF/lib directory.
> > The console web apps should not package any JARs, but instead use
> > dependency elements to add them to the class path.  ( e.g. console-
> > framework packages castor)
> >
> > --
> > This message is automatically generated by JIRA.
> > -
> > If you think it was sent incorrectly contact one of the
> > administrators: http://issues.apache.org/jira/secure/
> > Administrators.jspa
> > -
> > For more information on JIRA, see: http://www.atlassian.com/
> > software/jira
> >
> >
>
>

Reply via email to