You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by Scott Eade <se...@backstagetech.com.au> on 2006/06/20 01:48:42 UTC
Issue tracking
More admin I'm afraid...
There is a strong desire to shutdown the ASF Scarab instance - nothing
against Scarab, it is just that it is only used by a couple of
sub-projects and the resource usage in comparison to this and the fact
that there is nobody in infrastructure with the skills or desire to
maintain the instance means that it will most likely not be supported
for very much longer.
I'll look into getting Jira set up for JCS (the other choice is
bugzilla) - we can then revoke access to Scarab and migrate the issues
over (most likely manually).
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Issue tracking, Migrating JCS from Scarab to JIRA
Posted by Scott Eade <se...@backstagetech.com.au>.
I have submitted a request to infrastructure to migrate the issue
tracking for JCS from Scarab to JIRA:
http://issues.apache.org/jira/browse/INFRA-868
The migration instructions indicate that I need to inform the pmc of
this request and cc jira.
Scott
Scott Eade wrote:
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Issue tracking
Posted by Scott Eade <se...@backstagetech.com.au>.
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
Re: Issue tracking
Posted by Aaron Smuts <as...@yahoo.com>.
It think there is only one open issue in Scarab. It's
a feature that I created last night. I solved waht I
think was the only bug, yesterday. I wouldn't worry
about migrating anything.
--- Scott Eade <se...@backstagetech.com.au> wrote:
> More admin I'm afraid...
>
> There is a strong desire to shutdown the ASF Scarab
> instance - nothing
> against Scarab, it is just that it is only used by a
> couple of
> sub-projects and the resource usage in comparison to
> this and the fact
> that there is nobody in infrastructure with the
> skills or desire to
> maintain the instance means that it will most likely
> not be supported
> for very much longer.
>
> I'll look into getting Jira set up for JCS (the
> other choice is
> bugzilla) - we can then revoke access to Scarab and
> migrate the issues
> over (most likely manually).
>
> Scott
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail:
> jcs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org