Re: [VOTE][all] Switch to Jira
They need to be migrated over when Atlassian has a way to accomplish this (at least I heard there was no option yet to export a project and reimport it again in another jira instance) Mvgr, Martin Felipe Leme wrote: On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: +1 * For each of the 37 components ** Create new project - name: Commons Xxxx, key . What would happen with projects already on Jira, like Jelly? -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1.. Mvgr, Martin Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1 Jakarta Commons Developers List commons-dev@jakarta.apache.org wrote: +1.. Mvgr, Martin Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Find the home of your dreams with eircom net property Sign up for email alerts now http://www.eircom.net/propertyalerts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1 Jakarta Commons Developers List commons-dev@jakarta.apache.org wrote: +1.. Mvgr, Martin Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - Find the home of your dreams with eircom net property Sign up for email alerts now http://www.eircom.net/propertyalerts - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jelly] Migration effect Was: [VOTE][all] Switch to Jira
We're going to be in the same Jira as Jelly, so no ned for migrating etc. Hen On 5/3/06, Martin van den Bemt [EMAIL PROTECTED] wrote: They need to be migrated over when Atlassian has a way to accomplish this (at least I heard there was no option yet to export a project and reimport it again in another jira instance) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jelly] Migration effect Was: [VOTE][all] Switch to Jira
On the Jelly effect - I've renamed things in Jelly so that its permission scheme and developer group are Jakarta based and become the things that the rest of Commons will use. Should be unnoticeable from the Jelly point of view. Hen On 5/3/06, Henri Yandell [EMAIL PROTECTED] wrote: We're going to be in the same Jira as Jelly, so no ned for migrating etc. Hen On 5/3/06, Martin van den Bemt [EMAIL PROTECTED] wrote: They need to be migrated over when Atlassian has a way to accomplish this (at least I heard there was no option yet to export a project and reimport it again in another jira instance) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [jelly] Migration effect Was: [VOTE][all] Switch to Jira
Sorry for the confusion, thought it was running on codehaus... Mvgr, Martin Henri Yandell wrote: We're going to be in the same Jira as Jelly, so no ned for migrating etc. Hen On 5/3/06, Martin van den Bemt [EMAIL PROTECTED] wrote: They need to be migrated over when Atlassian has a way to accomplish this (at least I heard there was no option yet to export a project and reimport it again in another jira instance) Mvgr, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE][all] Switch to Jira
I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 +1 Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (MingW32) iD8DBQFEV5wvaCoPKRow/gARAnckAJ4gpIjxPeU3QUkbUWHnHrhtecjzeACg8YVx 0jKs8N9ovC1nrUi2w7e4/6o= =JWen -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE][all] Switch to Jira
+1 -Original Message- From: Henri Yandell [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 1:52 PM To: Jakarta Commons Developers List Subject: [VOTE][all] Switch to Jira I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1 On Tue, 2006-05-02 at 10:51 -0700, Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1 On 5/2/06, Oleg Kalnichevski [EMAIL PROTECTED] wrote: +1 On Tue, 2006-05-02 at 10:51 -0700, Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Davanum Srinivas : http://wso2.com/blogs/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [VOTE][all] Switch to Jira
+1 * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. This does not match: * Make Bugzilla read-only What about creating an 'Catch all' product in JIRA and only using JIRA? Gary -Original Message- From: Henri Yandell [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 02, 2006 10:52 AM To: Jakarta Commons Developers List Subject: [VOTE][all] Switch to Jira I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Jira migration Was: [VOTE][all] Switch to Jira
On 5/2/06, Gary Gregory [EMAIL PROTECTED] wrote: * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. This does not match: * Make Bugzilla read-only What about creating an 'Catch all' product in JIRA and only using JIRA? It would be. My fault for not saying Jira/Bugzilla when refering to the Commons project. We'd suck all the data into a project in Jira called Commons. Then we'd move stuff out of it into individual projects until we had just [site]/[all] issues left. Then we'd delete the versions and components in that Jira project and it becomes our catch-all Jira project. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [X] +1 [ ] -1 -- Martin Cooper Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira migration Was: [VOTE][all] Switch to Jira
On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: On 5/2/06, Gary Gregory [EMAIL PROTECTED] wrote: * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. This does not match: * Make Bugzilla read-only What about creating an 'Catch all' product in JIRA and only using JIRA? It would be. My fault for not saying Jira/Bugzilla when refering to the Commons project. We'd suck all the data into a project in Jira called Commons. Then we'd move stuff out of it into individual projects until we had just [site]/[all] issues left. Then we'd delete the versions and components in that Jira project and it becomes our catch-all Jira project. The problem with that is that you can be sure that plenty of people will file issues under something called just Commons without looking for the component. We'd be better off, IMHO, creating explicit components for 'site' and 'all'. (I'm not at all convinced we need the latter, though, since there would be issues with figuring out when it's ready to be marked Closed.) -- Martin Cooper Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1 Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira migration Was: [VOTE][all] Switch to Jira
On 5/2/06, Martin Cooper [EMAIL PROTECTED] wrote: On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: We'd suck all the data into a project in Jira called Commons. Then we'd move stuff out of it into individual projects until we had just [site]/[all] issues left. Then we'd delete the versions and components in that Jira project and it becomes our catch-all Jira project. The problem with that is that you can be sure that plenty of people will file issues under something called just Commons without looking for the component. We'd be better off, IMHO, creating explicit components for 'site' and 'all'. (I'm not at all convinced we need the latter, though, since there would be issues with figuring out when it's ready to be marked Closed.) It does sound likely. Looking at Bugzilla, there are 6 issues for [site], one of which was more to do with the build system. Let's go ahead and have a Commons Site project, and forget about the all bit, or keeping the Commons project used for the migration. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+0.5 Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
[X] +1 [ ] -1 cheers -- Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: +1 * For each of the 37 components ** Create new project - name: Commons Xxxx, key . What would happen with projects already on Jira, like Jelly? -- Felipe - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [X] +1 [ ] -1 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jelly] Migration effect Was: [VOTE][all] Switch to Jira
On 5/2/06, Felipe Leme [EMAIL PROTECTED] wrote: On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: +1 * For each of the 37 components ** Create new project - name: Commons Xxxx, key . What would happen with projects already on Jira, like Jelly? Good call. Move it to the Commons notification and permission schemes and put it in the Commons group. Shouldn't make much difference. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jira migration Was: [VOTE][all] Switch to Jira
Martin Cooper wrote: On 5/2/06, Henri Yandell [EMAIL PROTECTED] wrote: On 5/2/06, Gary Gregory [EMAIL PROTECTED] wrote: * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. This does not match: * Make Bugzilla read-only What about creating an 'Catch all' product in JIRA and only using JIRA? It would be. My fault for not saying Jira/Bugzilla when refering to the Commons project. We'd suck all the data into a project in Jira called Commons. Then we'd move stuff out of it into individual projects until we had just [site]/[all] issues left. Then we'd delete the versions and components in that Jira project and it becomes our catch-all Jira project. The problem with that is that you can be sure that plenty of people will file issues under something called just Commons without looking for the component. We'd be better off, IMHO, creating explicit components for 'site' and 'all'. (I'm not at all convinced we need the latter, though, since there would be issues with figuring out when it's ready to be marked Closed.) Use general for issues, that applies to all components. If a user creates an issue here (or anywhere else) where it does not belong - simply move it. JIRA creates internal redirects. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE][all] Switch to Jira
+1 Henri Yandell wrote: I'd like to call a vote that we switch to Jira. Here's the loose migration plan: * Make Bugzilla read-only * Import Commons project in Bugzilla into Commons project in JIRA This will pull over users, components, versions etc. * Setup notification scheme * Setup permission scheme * Setup group * For each of the 37 components ** Create new project - name: Commons Xxxx, key . ** Assign notification, permission and group ** Create relevant versions ** View component, bulk move all issues to new project * Cleanup Commons project (we'll still use it as a catch-all). Delete components/versions. The 37 components don't all have to be set up at the same time, we can take our time to move things out of the Commons project and into the individual Commons Foo projects. [ ] +1 [ ] -1 Vote to last 72 hours, 3 +1s required, 3/4 of active vote being +1. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
