You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Henning Schmiedehausen (JIRA)" <ji...@apache.org> on 2005/08/03 10:13:34 UTC
[jira] Created: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
---------------------------------------------------------------------------
Key: INFRA-479
URL: http://issues.apache.org/jira/browse/INFRA-479
Project: Infrastructure
Type: Task
Components: JIRA
Reporter: Henning Schmiedehausen
The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
Step one: Agree to move
We held a vote on turbine-dev which passed.
Step two: Bugzilla data
We don't use Bugzilla, we still use Scarab. Is data migration possible?
Step three: Project structure
We'd like to have a project category "TURBINE". As I understand, we can
add our own sub-cathegories later.
Step four: Pick Project keys
Main project key should be "TURBINE"
Step five: list of developers
JIRA Id -- Apache Login
henning -- henning@apache.org
Step six: Pick an Admin
henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-479?page=all ]
Henri Yandell reassigned INFRA-479:
-----------------------------------
Assign To: Henri Yandell
> Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
> ---------------------------------------------------------------------------
>
> Key: INFRA-479
> URL: http://issues.apache.org/jira/browse/INFRA-479
> Project: Infrastructure
> Type: Task
> Components: JIRA
> Reporter: Henning Schmiedehausen
> Assignee: Henri Yandell
>
> The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
> Step one: Agree to move
> We held a vote on turbine-dev which passed.
> Step two: Bugzilla data
> We don't use Bugzilla, we still use Scarab. Is data migration possible?
> Step three: Project structure
> We'd like to have a project category "TURBINE". As I understand, we can
> add our own sub-cathegories later.
> Step four: Pick Project keys
> Main project key should be "TURBINE"
> Step five: list of developers
> JIRA Id -- Apache Login
> henning -- henning@apache.org
> Step six: Pick an Admin
> henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-479?page=comments#action_12318642 ]
Henri Yandell commented on INFRA-479:
-------------------------------------
Jira project setup.
seade and henning both added to it.
> Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
> ---------------------------------------------------------------------------
>
> Key: INFRA-479
> URL: http://issues.apache.org/jira/browse/INFRA-479
> Project: Infrastructure
> Type: Task
> Components: JIRA
> Reporter: Henning Schmiedehausen
> Assignee: Henri Yandell
>
> The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
> Step one: Agree to move
> We held a vote on turbine-dev which passed.
> Step two: Bugzilla data
> We don't use Bugzilla, we still use Scarab. Is data migration possible?
> Step three: Project structure
> We'd like to have a project category "TURBINE". As I understand, we can
> add our own sub-cathegories later.
> Step four: Pick Project keys
> Main project key should be "TURBINE"
> Step five: list of developers
> JIRA Id -- Apache Login
> henning -- henning@apache.org
> Step six: Pick an Admin
> henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Posted by "Henning Schmiedehausen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-479?page=comments#action_12317510 ]
Henning Schmiedehausen commented on INFRA-479:
----------------------------------------------
Additional User
JIRA Id -- Apache Login
seade -- seade@apache.org
> Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
> ---------------------------------------------------------------------------
>
> Key: INFRA-479
> URL: http://issues.apache.org/jira/browse/INFRA-479
> Project: Infrastructure
> Type: Task
> Components: JIRA
> Reporter: Henning Schmiedehausen
>
> The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
> Step one: Agree to move
> We held a vote on turbine-dev which passed.
> Step two: Bugzilla data
> We don't use Bugzilla, we still use Scarab. Is data migration possible?
> Step three: Project structure
> We'd like to have a project category "TURBINE". As I understand, we can
> add our own sub-cathegories later.
> Step four: Pick Project keys
> Main project key should be "TURBINE"
> Step five: list of developers
> JIRA Id -- Apache Login
> henning -- henning@apache.org
> Step six: Pick an Admin
> henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Posted by "Henning Schmiedehausen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-479?page=comments#action_12318590 ]
Henning Schmiedehausen commented on INFRA-479:
----------------------------------------------
Any progress on this? Whom do I ping directly?
> Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
> ---------------------------------------------------------------------------
>
> Key: INFRA-479
> URL: http://issues.apache.org/jira/browse/INFRA-479
> Project: Infrastructure
> Type: Task
> Components: JIRA
> Reporter: Henning Schmiedehausen
>
> The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
> Step one: Agree to move
> We held a vote on turbine-dev which passed.
> Step two: Bugzilla data
> We don't use Bugzilla, we still use Scarab. Is data migration possible?
> Step three: Project structure
> We'd like to have a project category "TURBINE". As I understand, we can
> add our own sub-cathegories later.
> Step four: Pick Project keys
> Main project key should be "TURBINE"
> Step five: list of developers
> JIRA Id -- Apache Login
> henning -- henning@apache.org
> Step six: Pick an Admin
> henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-479?page=all ]
Henri Yandell closed INFRA-479:
-------------------------------
Resolution: Fixed
Should all be done. The only part not done is the Scarab migration; but that's a whole different ballpark that'll want to be its own issue if Turbine don't just copy the issues they want to keep over.
> Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
> ---------------------------------------------------------------------------
>
> Key: INFRA-479
> URL: http://issues.apache.org/jira/browse/INFRA-479
> Project: Infrastructure
> Type: Task
> Components: JIRA
> Reporter: Henning Schmiedehausen
> Assignee: Henri Yandell
>
> The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
> Step one: Agree to move
> We held a vote on turbine-dev which passed.
> Step two: Bugzilla data
> We don't use Bugzilla, we still use Scarab. Is data migration possible?
> Step three: Project structure
> We'd like to have a project category "TURBINE". As I understand, we can
> add our own sub-cathegories later.
> Step four: Pick Project keys
> Main project key should be "TURBINE"
> Step five: list of developers
> JIRA Id -- Apache Login
> henning -- henning@apache.org
> Step six: Pick an Admin
> henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (INFRA-479) Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
Posted by "Henri Yandell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/INFRA-479?page=comments#action_12318643 ]
Henri Yandell commented on INFRA-479:
-------------------------------------
I used Tapestry as an template (it's easies to copy when creating in Jira).
This means that by default all turbine developers will be turbine admins.
I left the from address for email notification as jira@apache.org; not sure what the advantage of having Tapestry's be tapestry-dev@jakarta.apache.org is.
> Create JIRA project for Jakarta Turbine and move old Bugtracker from Scarab
> ---------------------------------------------------------------------------
>
> Key: INFRA-479
> URL: http://issues.apache.org/jira/browse/INFRA-479
> Project: Infrastructure
> Type: Task
> Components: JIRA
> Reporter: Henning Schmiedehausen
> Assignee: Henri Yandell
>
> The Jakarta Turbine Project has decided to move its bugtracker from Scarab to JIRA.
> Step one: Agree to move
> We held a vote on turbine-dev which passed.
> Step two: Bugzilla data
> We don't use Bugzilla, we still use Scarab. Is data migration possible?
> Step three: Project structure
> We'd like to have a project category "TURBINE". As I understand, we can
> add our own sub-cathegories later.
> Step four: Pick Project keys
> Main project key should be "TURBINE"
> Step five: list of developers
> JIRA Id -- Apache Login
> henning -- henning@apache.org
> Step six: Pick an Admin
> henning -- henning@apache.org -- Jakarta PMC member
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira