On 27 Oct 2005, at 15:55, Vadim Gritsenko wrote:
Bertrand Delacretaz (JIRA) wrote:Release 2.1.8 ------------- Key: COCOON-1663 URL: http://issues.apache.org/jira/browse/COCOON-1663 Project: Cocoon Type: TaskVersions: 2.1.8-dev (Current SVN) Reporter: Bertrand Delacretaz Assigned to: Cocoon Developers Team This issue depends on other issues which we consider blocking for the releaseIIUC that's not the Jira way to do it... Am I right? Pier? :)
No, it is not... But Bertrand was right, as I forgot to add one thing in our "reduced" configuration.
The missing field was "Fix Version/s", which basically defines in what version the bug should be fixed.
If you look now at this report:http://issues.apache.org/jira/browse/COCOON? report=com.atlassian.jira.plugin.system.project:roadmap-panel
This will indicate that we have issue 1483 FIXED in 2.1.8 dev, while issue 1594, which is "scheduled" for 2.1.8 (the "Fix Version/s" field is set to that value) hasn't been fixed yet...
So, as far as I can see, we're at 50% of our roadmap.I will add also those other bugs that came up in the discussion, with the correct versions, so, keep looking at that report!
Pier
smime.p7s
Description: S/MIME cryptographic signature
