jakarta-jcs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Scott Eade <se...@backstagetech.com.au>
Subject Re: Issue tracking
Date Tue, 20 Jun 2006 01:01:37 GMT
Okay I am looking at 
http://wiki.apache.org/general/ApacheBugzillaToJiraMigration for 
direction - it gives a bunch of steps.

Step 1: Agree to move.
I'm going to take this a s a given - feel free to -1 if you disagree.

Step 2: Do we want to migrate the existing data.
I suggest we just transfer the open issues manually - there are not that 
many of them.
If there are any open issues that can be closed then please do so (we 
will only migrate the open issues).

Step 3: Project structure.
I think we want one project named "JCS" (though of course we are part of 
Jakarta).

Step 4: Pick project key.
"JCS"

Step 5: List of developers.
Aaron Smuts - asmuts@apache.org
Hanson Char - hchar@apache.org
Travis Savo - tsavo@ifilm.com
Scott Eade - seade@backstagetech.com.au

Step 6: Pick an administrator
Scott Eade - seade@backstagetech.com.au (for now, can switch over to 
Aaron after setup)

Step 7: Enter a request in JIRA
Details will include:
- Vote results - no vote taken
- Whether you want to import bugzilla data:? No
- List of projects with keys: JCS (key: JCS)
- email address to send notifications: jcs-dev@jakarta.apache.org
- email address of administrator: seade@backstagetech.com.au
- project category: Jakarta
- permission scheme: Jakarta permissions

Does anyone have any comments before I submit this request.

Scott

-- 
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au


---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org


Mime
View raw message