www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Turner (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-737) Please upgrade to JIRA 3.5
Date Wed, 22 Feb 2006 11:47:38 GMT
    [ http://issues.apache.org/jira/browse/INFRA-737?page=comments#action_12367333 ] 

Jeff Turner commented on INFRA-737:
-----------------------------------

I am not keen to upgrade to 3.5 just yet as experience elsewhere (on jira.atlassian.com) suggests
3.5.x has a memory leak. It doesn't affect many people apparently, but issues.apache.org is
not the box to dice with memory leaks on because its Itanium architecture precludes use of
most profilers.

It is possible to write a jelly script to close a list of issues:

http://www.atlassian.com/software/jira/docs/v3.3.2/jelly.html#TransitionWorkflow

However, does MyFaces really need to distinguish between 'Resolved' and 'Closed'? Most other
projects don't. The only practical difference is that closed issues can't be edited, which
is occasionally annoying when someone wants to change a component, 'affects' version or other
detail on a fixed issue. And besides, closing all resolved issues will generate a storm of
notification emails.

> Please upgrade to JIRA 3.5
> --------------------------
>
>          Key: INFRA-737
>          URL: http://issues.apache.org/jira/browse/INFRA-737
>      Project: Infrastructure
>         Type: Wish
>   Components: JIRA
>     Reporter: sean schofield

>
> The MyFaces project requests that we upgrade JIRA at the soonest possible point in time.
 There is a critical issue (http://jira.atlassian.com/browse/JRA-2427) that has been fixed.
 You can see by the number of votes that its hugely important.  This will allow projects to
do bulk updates to convert all resolved issues and changed them to closed when a release becomes
official.  We desperately need that feature as doing this by hand is impossible.
> I'd be happy to help with the upgrade if there is anything I can do as a committer. 
At a minimum I would certainly volunteer to help test.
> Upgrade instructions for 3.3.x version can be found here: http://confluence.atlassian.com/display/JIRA/All+JIRA+3.x+Upgrade+Guides

-- 
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


Mime
View raw message