You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2005/10/27 16:48:55 UTC
[jira] Created: (COCOON-1663) Release 2.1.8
Release 2.1.8
-------------
Key: COCOON-1663
URL: http://issues.apache.org/jira/browse/COCOON-1663
Project: Cocoon
Type: Task
Versions: 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 release
--
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
Re: [jira] Created: (COCOON-1663) Release 2.1.8
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Bertrand Delacretaz wrote:
> Le 27 oct. 05, à 16:55, Vadim Gritsenko a écrit :
>
>> IIUC that's not the Jira way to do it... Am I right? Pier? :)
>
> I'm open to other suggestions for sure, if people who know jira better
> want to do it then go ahead, I won't mind!
http://www.atlassian.com/software/jira/docs/v3.2/issue_scheduling.html
Jira admin should give committers "Schedule Issues" permission, so than we can
schedule issues to releases - will appear on the "Road Map".
Vadim
Re: [jira] Created: (COCOON-1663) Release 2.1.8
Posted by Bertrand Delacretaz <bd...@apache.org>.
Le 27 oct. 05, à 16:55, Vadim Gritsenko a écrit :
> IIUC that's not the Jira way to do it... Am I right? Pier? :)
It would work, though ;-)
I'm open to other suggestions for sure, if people who know jira better
want to do it then go ahead, I won't mind!
The point is: managing these things in the issue tracker would make our
life easier, and leave a much better trace of the release process.
-Bertrand
Re: [jira] Created: (COCOON-1663) Release 2.1.8
Posted by Pier Fumagalli <pi...@betaversion.org>.
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: Task
>> Versions: 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 release
>
> IIUC 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
Re: [jira] Created: (COCOON-1663) Release 2.1.8
Posted by Vadim Gritsenko <va...@reverycodes.com>.
Bertrand Delacretaz (JIRA) wrote:
> Release 2.1.8
> -------------
>
> Key: COCOON-1663
> URL: http://issues.apache.org/jira/browse/COCOON-1663
> Project: Cocoon
> Type: Task
> Versions: 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 release
>
IIUC that's not the Jira way to do it... Am I right? Pier? :)
Vadim
[jira] Commented: (COCOON-1663) Release 2.1.8
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1663?page=comments#action_12356092 ]
Bertrand Delacretaz commented on COCOON-1663:
---------------------------------------------
To mark an issue as blocking for the 2.1.8 release, use the "links" function of the blocking issue.
> Release 2.1.8
> -------------
>
> Key: COCOON-1663
> URL: http://issues.apache.org/jira/browse/COCOON-1663
> Project: Cocoon
> Type: Task
> Versions: 2.1.8-dev (Current SVN)
> Reporter: Bertrand Delacretaz
> Assignee: Cocoon Developers Team
>
> This issue depends on other issues which we consider blocking for the release
--
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
[jira] Updated: (COCOON-1663) Release 2.1.8
Posted by "Bertrand Delacretaz (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Bertrand Delacretaz updated COCOON-1663:
----------------------------------------
Comment: was deleted
> Release 2.1.8
> -------------
>
> Key: COCOON-1663
> URL: http://issues.apache.org/jira/browse/COCOON-1663
> Project: Cocoon
> Type: Task
> Versions: 2.1.8-dev (Current SVN)
> Reporter: Bertrand Delacretaz
> Assignee: Cocoon Developers Team
>
> This issue depends on other issues which we consider blocking for the release
--
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
[jira] Updated: (COCOON-1663) Release 2.1.8
Posted by "Pier Fumagalli (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/COCOON-1663?page=all ]
Pier Fumagalli updated COCOON-1663:
-----------------------------------
Fix Version: 2.1.8-dev (Current SVN)
> Release 2.1.8
> -------------
>
> Key: COCOON-1663
> URL: http://issues.apache.org/jira/browse/COCOON-1663
> Project: Cocoon
> Type: Task
> Versions: 2.1.8-dev (Current SVN)
> Reporter: Bertrand Delacretaz
> Assignee: Cocoon Developers Team
> Fix For: 2.1.8-dev (Current SVN)
>
> This issue depends on other issues which we consider blocking for the release
--
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