You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jerry Cwiklik (JIRA)" <de...@uima.apache.org> on 2011/02/23 22:56:38 UTC
[jira] Updated: (UIMA-2071) Change sort order of issues in UIMA AS
JIRA report
[ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jerry Cwiklik updated UIMA-2071:
--------------------------------
Fix Version/s: 2.3.2SDK
> Change sort order of issues in UIMA AS JIRA report
> --------------------------------------------------
>
> Key: UIMA-2071
> URL: https://issues.apache.org/jira/browse/UIMA-2071
> Project: UIMA
> Issue Type: Improvement
> Components: Async Scaleout
> Reporter: Jerry Cwiklik
> Assignee: Jerry Cwiklik
> Priority: Minor
> Fix For: 2.3.1AS, 2.3.2SDK
>
>
> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [jira] Updated: (UIMA-2071) Change sort order of issues in UIMA
AS JIRA report
Posted by Marshall Schor <ms...@schor.com>.
The issue here is that Apache infrastructure recently upgraded our Jira
installation. This had a side effect, in that the treatment of the sequence of
keys to use for sorting, was reversed in the newer Jira.
UIMA SDK 2.3.1 was released (and therefore the issuesFixed set was generated)
using the older, previous Jira.
This fix will keep the same sort as we used in the 2.3.1 release, now that it's
being run against the upgraded Jira.
I hope that explains it :-) -Marshall
On 2/23/2011 4:57 PM, Jörn Kottmann wrote:
> Don't we do that for 2.3.1 ?
>
> Jörn
>
> On 2/23/11 10:56 PM, Jerry Cwiklik (JIRA) wrote:
>> [
>> https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>> ]
>>
>> Jerry Cwiklik updated UIMA-2071:
>> --------------------------------
>>
>> Fix Version/s: 2.3.2SDK
>>
>>> Change sort order of issues in UIMA AS JIRA report
>>> --------------------------------------------------
>>>
>>> Key: UIMA-2071
>>> URL: https://issues.apache.org/jira/browse/UIMA-2071
>>> Project: UIMA
>>> Issue Type: Improvement
>>> Components: Async Scaleout
>>> Reporter: Jerry Cwiklik
>>> Assignee: Jerry Cwiklik
>>> Priority: Minor
>>> Fix For: 2.3.1AS, 2.3.2SDK
>>>
>>>
>>> UIMA AS JIRA report is currently sorted in ascending order - oldest issues
>>> first. Change the order to newest first.
>
>
>
Re: [jira] Updated: (UIMA-2071) Change sort order of issues in UIMA
AS JIRA report
Posted by Jörn Kottmann <ko...@gmail.com>.
Don't we do that for 2.3.1 ?
Jörn
On 2/23/11 10:56 PM, Jerry Cwiklik (JIRA) wrote:
> [ https://issues.apache.org/jira/browse/UIMA-2071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>
> Jerry Cwiklik updated UIMA-2071:
> --------------------------------
>
> Fix Version/s: 2.3.2SDK
>
>> Change sort order of issues in UIMA AS JIRA report
>> --------------------------------------------------
>>
>> Key: UIMA-2071
>> URL: https://issues.apache.org/jira/browse/UIMA-2071
>> Project: UIMA
>> Issue Type: Improvement
>> Components: Async Scaleout
>> Reporter: Jerry Cwiklik
>> Assignee: Jerry Cwiklik
>> Priority: Minor
>> Fix For: 2.3.1AS, 2.3.2SDK
>>
>>
>> UIMA AS JIRA report is currently sorted in ascending order - oldest issues first. Change the order to newest first.