openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Prud'hommeaux <mprud...@apache.org>
Subject Re: annotations / tags in JIRA?
Date Sat, 07 Apr 2007 00:16:00 GMT

+1

On Apr 6, 2007, at 5:13 PM, Patrick Linskey wrote:

> So I was thinking that a similar concept would be useful for tracking
> things that need more documentation or release notes. I poked around
> JIRA a bit, and discovered that it's possible to create custom fields.
> Derby has a multi-checkbox custom field that includes the following:
>
> _ Patch Available
> _ Existing Application Impact
> _ Regression
> _ Release Note Needed
>
> I'm thinking that it'd be good to add a new 'Documentation Needed'
> checkbox to their 'Derby Info' custom field, lobby them to change the
> name to 'Additional Flags' or something, and use that in OpenJPA as
> well.
>
> Since JIRA limits the number of available custom fields, I think that
> the umbrella-issue approach is probably appropriate enough for JPA2
> follow-up. But it seems like things like release note status and
> documentation status are things that are useful to many projects.
>
> Thoughts?
>
> -Patrick
>
> --  
> Patrick Linskey
> BEA Systems, Inc.
>
> ______________________________________________________________________ 
> _
> Notice:  This email message, together with any attachments, may  
> contain
> information  of  BEA Systems,  Inc.,  its subsidiaries  and   
> affiliated
> entities,  that may be confidential,  proprietary,  copyrighted   
> and/or
> legally privileged, and is intended solely for the use of the  
> individual
> or entity named in this message. If you are not the intended  
> recipient,
> and have received this message in error, please immediately return  
> this
> by email and then delete it.
>
>> -----Original Message-----
>> From: Patrick Linskey [mailto:plinskey@bea.com]
>> Sent: Thursday, April 05, 2007 1:32 PM
>> To: open-jpa-dev@incubator.apache.org
>> Subject: annotations / tags in JIRA?
>>
>> Hi,
>>
>> Is it possible to annotate issues in JIRA with some sort of  
>> structured
>> or semi-structured tag? I'd like to be able to mark
>> OPENJPA-204 so that
>> we can come back to it later when working on the next JPA
>> specification
>> version. I guess I could clone the issue and either make a new issue
>> type or a new component, but it seems like it'd be convenient to just
>> mark it as "JPA2-followup" or something like that.
>>
>> -Patrick
>>
>> -- 
>> Patrick Linskey
>> BEA Systems, Inc.
>>
>> ______________________________________________________________
>> _________
>> Notice:  This email message, together with any attachments,
>> may contain
>> information  of  BEA Systems,  Inc.,  its subsidiaries  and
>> affiliated
>> entities,  that may be confidential,  proprietary,
>> copyrighted  and/or
>> legally privileged, and is intended solely for the use of the
>> individual
>> or entity named in this message. If you are not the intended
>> recipient,
>> and have received this message in error, please immediately
>> return this
>> by email and then delete it.
>>
>> Notice:  This email message, together with any attachments,
>> may contain information  of  BEA Systems,  Inc.,  its
>> subsidiaries  and  affiliated entities,  that may be
>> confidential,  proprietary,  copyrighted  and/or legally
>> privileged, and is intended solely for the use of the
>> individual or entity named in this message. If you are not
>> the intended recipient, and have received this message in
>> error, please immediately return this by email and then delete it.
>>
>
> Notice:  This email message, together with any attachments, may  
> contain information  of  BEA Systems,  Inc.,  its subsidiaries   
> and  affiliated entities,  that may be confidential,  proprietary,   
> copyrighted  and/or legally privileged, and is intended solely for  
> the use of the individual or entity named in this message. If you  
> are not the intended recipient, and have received this message in  
> error, please immediately return this by email and then delete it.


Mime
View raw message