You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by Grzegorz Kossakowski <gr...@tuffmail.com> on 2007/09/18 11:12:52 UTC
Initial content for our custom JIRA fields
Hi again,
I have some good news. We have finally our custom fields for per-component versions, see
INFRA-1361[1]! Only one glitch about them is that only JIRA Admin (not Project Admin) can edit
values stored in this fields. Fortunately enough Carsten has necessary karma and he agreed to manage
them (at least to some extent, see comments on INFRA-1361).
I decided to collect initial data that these fields should be filled with. You may want to take into
account that this list is NOT final by any means and feel free to add anything I forgot about. The
list is (I put versions in brackets):
* Cocoon core (2.2.0-M1, 2.2.0-M2, 2.2.0-M3, 2.2.0-RC1)
- Components: Sitemap (1.0.0-M1, 1.0.0-RC1)
- Components: Pipeline (1.0.0-M1, 1.0.0-RC1)
- Expression language (1.0.0-M1)
Blocks: Ajax (1.0.0-M1, 1.0.0-M2, 1.0.0-M3)
Blocks: Apples (1.0.0-M1, 1.0.0-M2, 1.0.0-RC1)
Blocks: Authentication (1.0.0-M1, 1.0.0-RC1)
Blocks: Batik (1.0.0-M1, 1.0.0-RC1)
Blocks: Captcha (1.0.0-M1, 1.0.0-RC1)
Blocks: Databases (1.0.0-M1, 1.0.0-RC1)
Blocks: Flowscript (1.0.0-M1, 1.0.0-M2, 1.0.0-M3)
Blocks: FOP (1.0.0-M1, 1.0.0-RC1)
Blocks: Forms (1.0.0-M1, 1.0.0-M2, 1.0.0-M3)
Blocks: HTML (1.0.0-M1, 1.0.0-RC1)
Blocks: Linkrewriter (1.0.0-M1, 1.0.0-RC1)
Blocks: Mail (1.0.0-M1, 1.0.0-RC1)
Blocks: Template (1.0.0-M1, 1.0.0-M2, 1.0.0-M3, 1.0.0-RC1)
Maven Block Archetype (1.0.0-M1, 1.0.0-M2, 1.0.0-M3, 1.0.0-M4, 1.0.0-M5, 1.0.0-RC1)
Maven Webapp Archetype (1.0.0-M1, 1.0.0-M2, 1.0.0-RC1)
Maven Cocoon plug-in (1.0.0-M1)
Subproject: Servlet Service Fw (1.0.0-M1, 1.0.0-M2)
Subproject: Cocoon Configuration (1.0.0)
I hope that this covers most things.
Carsten, when will you be able to add this list?
Thanks in advance.
[1] https://issues.apache.org/jira/browse/INFRA-1361
--
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/
Re: Initial content for our custom JIRA fields
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Carsten Ziegeler pisze:
>>
> I can do this any day during this week (most preferably thursday or
> saturday). Just to be sure, what I should do:
> the idea is to add *all* version numbers to both fields, right?
Yes, but our custom fields are of cascading type. This means that you can assign separate version
sets for each component.
Anyway, values of both fields should be exactly the same.
--
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/
Re: Initial content for our custom JIRA fields
Posted by Carsten Ziegeler <cz...@apache.org>.
Grzegorz Kossakowski wrote
>
> We have cascading fields so you can add modules (components) and versions separately.
> See
> http://www.atlassian.com/software/jira/docs/v3.2/customfields/overview.html#Custom+field+configuration+schemes
>
D'oh - sure.
Okay, I've added the initial set - if you find any problems, typos etc.
let me know.
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Initial content for our custom JIRA fields
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Carsten Ziegeler pisze:
> Grzegorz Kossakowski wrote:
>> Carsten Ziegeler pisze:
>> Carsten, any news on this? I'm rush you because it's period when we can't commit now and I would
>> like to spend some of my free time on documenting and planning. Actually, we should seriously start
>> considering making Cocoon 2.2 final and Cocoon 2.1.11.
>>
>> My idea is to mark issues that are needed to be fixed before we can make both releases. Then, I
>> think we should call people for to vote for issues they would love to have fixed in Cocoon 2.1.12
>> while telling them we are going to close 2.1.x branch at the time making Cocoon 2.1.12 release.
>>
>> Ok, getting little bit off-topic. In short: Carsten, I just wanted to shuffle your priority list a
>> little if possible :-)
>>
> Ok, I can add these now, final question though - I assume I only add
> versions, right? (Or should I add version together with the module name?)
> For example in the case of Ajax, to I just add 1.0.0-M1, 1.0.0-M2 and
> 1.0.0-M3 or is it Ajax 1.0.0-M1, etc.?
We have cascading fields so you can add modules (components) and versions separately.
See
http://www.atlassian.com/software/jira/docs/v3.2/customfields/overview.html#Custom+field+configuration+schemes
--
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/
Re: Initial content for our custom JIRA fields
Posted by Carsten Ziegeler <cz...@apache.org>.
Grzegorz Kossakowski wrote:
> Carsten Ziegeler pisze:
>> I can do this any day during this week (most preferably thursday or
>> saturday). Just to be sure, what I should do:
>> the idea is to add *all* version numbers to both fields, right?
>
> Carsten, any news on this? I'm rush you because it's period when we can't commit now and I would
> like to spend some of my free time on documenting and planning. Actually, we should seriously start
> considering making Cocoon 2.2 final and Cocoon 2.1.11.
>
> My idea is to mark issues that are needed to be fixed before we can make both releases. Then, I
> think we should call people for to vote for issues they would love to have fixed in Cocoon 2.1.12
> while telling them we are going to close 2.1.x branch at the time making Cocoon 2.1.12 release.
>
> Ok, getting little bit off-topic. In short: Carsten, I just wanted to shuffle your priority list a
> little if possible :-)
>
Ok, I can add these now, final question though - I assume I only add
versions, right? (Or should I add version together with the module name?)
For example in the case of Ajax, to I just add 1.0.0-M1, 1.0.0-M2 and
1.0.0-M3 or is it Ajax 1.0.0-M1, etc.?
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Initial content for our custom JIRA fields
Posted by Grzegorz Kossakowski <gk...@apache.org>.
Carsten Ziegeler pisze:
> I can do this any day during this week (most preferably thursday or
> saturday). Just to be sure, what I should do:
> the idea is to add *all* version numbers to both fields, right?
Carsten, any news on this? I'm rush you because it's period when we can't commit now and I would
like to spend some of my free time on documenting and planning. Actually, we should seriously start
considering making Cocoon 2.2 final and Cocoon 2.1.11.
My idea is to mark issues that are needed to be fixed before we can make both releases. Then, I
think we should call people for to vote for issues they would love to have fixed in Cocoon 2.1.12
while telling them we are going to close 2.1.x branch at the time making Cocoon 2.1.12 release.
Ok, getting little bit off-topic. In short: Carsten, I just wanted to shuffle your priority list a
little if possible :-)
--
Grzegorz Kossakowski
Committer and PMC Member of Apache Cocoon
http://reflectingonthevicissitudes.wordpress.com/
Re: Initial content for our custom JIRA fields
Posted by Carsten Ziegeler <cz...@apache.org>.
Grzegorz Kossakowski schrieb:
> Hi again,
>
> I have some good news. We have finally our custom fields for per-component versions, see
> INFRA-1361[1]! Only one glitch about them is that only JIRA Admin (not Project Admin) can edit
> values stored in this fields. Fortunately enough Carsten has necessary karma and he agreed to manage
> them (at least to some extent, see comments on INFRA-1361).
>
> I decided to collect initial data that these fields should be filled with. You may want to take into
> account that this list is NOT final by any means and feel free to add anything I forgot about. The
> list is (I put versions in brackets):
> * Cocoon core (2.2.0-M1, 2.2.0-M2, 2.2.0-M3, 2.2.0-RC1)
> - Components: Sitemap (1.0.0-M1, 1.0.0-RC1)
> - Components: Pipeline (1.0.0-M1, 1.0.0-RC1)
> - Expression language (1.0.0-M1)
> Blocks: Ajax (1.0.0-M1, 1.0.0-M2, 1.0.0-M3)
> Blocks: Apples (1.0.0-M1, 1.0.0-M2, 1.0.0-RC1)
> Blocks: Authentication (1.0.0-M1, 1.0.0-RC1)
> Blocks: Batik (1.0.0-M1, 1.0.0-RC1)
> Blocks: Captcha (1.0.0-M1, 1.0.0-RC1)
> Blocks: Databases (1.0.0-M1, 1.0.0-RC1)
> Blocks: Flowscript (1.0.0-M1, 1.0.0-M2, 1.0.0-M3)
> Blocks: FOP (1.0.0-M1, 1.0.0-RC1)
> Blocks: Forms (1.0.0-M1, 1.0.0-M2, 1.0.0-M3)
> Blocks: HTML (1.0.0-M1, 1.0.0-RC1)
> Blocks: Linkrewriter (1.0.0-M1, 1.0.0-RC1)
> Blocks: Mail (1.0.0-M1, 1.0.0-RC1)
> Blocks: Template (1.0.0-M1, 1.0.0-M2, 1.0.0-M3, 1.0.0-RC1)
> Maven Block Archetype (1.0.0-M1, 1.0.0-M2, 1.0.0-M3, 1.0.0-M4, 1.0.0-M5, 1.0.0-RC1)
> Maven Webapp Archetype (1.0.0-M1, 1.0.0-M2, 1.0.0-RC1)
> Maven Cocoon plug-in (1.0.0-M1)
> Subproject: Servlet Service Fw (1.0.0-M1, 1.0.0-M2)
> Subproject: Cocoon Configuration (1.0.0)
>
> I hope that this covers most things.
> Carsten, when will you be able to add this list?
>
I can do this any day during this week (most preferably thursday or
saturday). Just to be sure, what I should do:
the idea is to add *all* version numbers to both fields, right?
Carsten
--
Carsten Ziegeler
cziegeler@apache.org