cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joerg Heinicke <joerg.heini...@gmx.de>
Subject versions in Jira
Date Thu, 04 Jan 2007 23:46:13 GMT
On 05.01.2007 00:21, Jörg Heinicke (JIRA) wrote:

>        Resolution: Fixed
>     Fix Version/s: 2.2-dev (Current SVN)
>                    2.1.11-dev (current SVN)

I wonder how we manage those versions. It seems to be quite strange:
Issues fixed in 2.1.9: https://issues.apache.org/jira/browse/COCOON-1700
https://issues.apache.org/jira/browse/COCOON-1806
In 2.1.10: https://issues.apache.org/jira/browse/COCOON-1879
In 2.1.11-dev: https://issues.apache.org/jira/browse/COCOON-1977

It seems that both the renaming and the handling of the properties 
themselves are done wrongly:

1. 2.1.9-dev got correctly renamed to 2.1.9, but having 2.1.9-dev in 
"Affects Versions" lets it view quite strange as the bug seems to be in 
2.1.9 and is fixed in that version as well.
2. For 2.1.10-dev it seems to be even worse. I guess it was directly 
renamed to 2.1.11-dev - which now makes all version infos in those bugs 
wrong.

How it must be handled:
1. As soon as a bug gets fixed the "Current SVN" version MUST be removed 
from "Affects versions". As it is already fixed having it there is also 
no longer correct.
2. The X.Y.Z-dev version must be renamed to X.Y.Z after a release and a 
new entry created for X.Y.Z+1-dev and not the other way around.

Otherwise we provide wrong information on issues in Jira.

I'll fix the above for 2.1.10-dev => 2.1.11-dev.

Jörg

Mime
View raw message