cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grzegorz Kossakowski <gkossakow...@apache.org>
Subject Re: [VOTE] Introduce component/module specific version fields in JIRA
Date Mon, 27 Aug 2007 12:14:09 GMT
Grzegorz Kossakowski pisze:
> Joerg Heinicke pisze:
>> On 26.08.2007 7:29 Uhr, Grzegorz Kossakowski wrote:
>>
>>> Unexpectedly, Nils Kaiser has come up with much better and, in
>>> general, less intrusive solution. He
>>> proposed[3] to introduce custom fields where information about version
>>> specific to the *component*
>>> would be stored.
>> I don't want to rain on the party again, but have you checked the
>> approach with infrastructure team? I fear this effects all projects and
>> I'm not sure they want to do this.
> 
> I checked this here:
> http://www.atlassian.com/software/jira/docs/v3.2/customfields/overview.html#Custom+field+context
> 
> However, I was sure that we have the most recent version of JIRA, here on Apache. According
to the
> footer I was wrong, we are still using 3.1.x...
> 
> Without custom field contexts you are probably right, all projects will be affected.
On the other
> hand, we already have custom fields (if patch is attached or bugzilla id) that do not
appear in
> other projects. Do someone knows how it works?

Ok, I'm LAME! :-D

On Apache we use JIRA 3.10.x not 3.1.x so there will be no problem with our custom fields.

-- 
Grzegorz Kossakowski
http://reflectingonthevicissitudes.wordpress.com/

Mime
View raw message