Re: [jelly] Migration effect Was: [VOTE][all] Switch to Jira

2006-05-03 Thread Henri Yandell
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

Re: [jelly] Migration effect Was: [VOTE][all] Switch to Jira

2006-05-03 Thread Henri Yandell
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

Re: [jelly] Migration effect Was: [VOTE][all] Switch to Jira

2006-05-03 Thread Martin van den Bemt
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

[jelly] Migration effect Was: [VOTE][all] Switch to Jira

2006-05-02 Thread Henri Yandell
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