I'm just warning that unless those issues are actually fixed in that version that there is going to be a bunch of work needed to properly sort out jira when it comes release time.

--jason


On Oct 10, 2006, at 1:51 PM, Aaron Mulder wrote:

Isn't the point of a road map to show what's coming / targeted for
each release?  Otherwise, it's release notes, not a road map.  I feel
pretty strongly that we should have some way for Jira to present a
list of the issues targeted to be included in each release.  Do you
have an alternative to the road map to suggest?

Thanks,
     Aaron

On 10/10/06, Jason Dillon <[EMAIL PROTECTED]> wrote:
Its not about what version you believe it should be fixed in... fixed
versions is for what version it was actually fixed in.  This value is
used to generate the change log in the roadmap and if the issue is
not actually fixed in that version it just pollutes the details that
jira shows us.

For example, if this issue is not actually fixed in 1.1.2, but
instead fixed in 1.1.3, then there is some confusion when inspecting
the roadmap for what was fixed where.

--jason


On Oct 10, 2006, at 1:33 PM, Aaron Mulder 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