You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Henri Yandell <fl...@gmail.com> on 2006/05/02 19:51:33 UTC
[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 "XXXX".
** 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Dennis Lundberg <de...@apache.org>.
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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Martin van den Bemt <ml...@mvdb.net>.
+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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Don Brown <do...@gmail.com>.
+1
On 5/2/06, Henri Yandell <fl...@gmail.com> 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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: [VOTE][all] Switch to Jira
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEV5wvaCoPKRow/gARAnckAJ4gpIjxPeU3QUkbUWHnHrhtecjzeACg8YVx
0jKs8N9ovC1nrUi2w7e4/6o=
=JWen
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Martin Cooper <ma...@apache.org>.
On 5/2/06, Henri Yandell <fl...@gmail.com> 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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
Re: [VOTE][all] Switch to Jira
Posted by Torsten Curdt <tc...@apache.org>.
> > [X] +1
> > [ ] -1
cheers
--
Torsten
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Brett Porter <br...@apache.org>.
+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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Stephen Colebourne <sc...@btopenworld.com>.
+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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Martin van den Bemt <ml...@mvdb.net>.
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 <fl...@gmail.com> 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 "XXXX".
>
>
> What would happen with projects already on Jira, like Jelly?
>
> -- Felipe
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Felipe Leme <fe...@gmail.com>.
On 5/2/06, Henri Yandell <fl...@gmail.com> 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 "XXXX".
What would happen with projects already on Jira, like Jelly?
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Jörg Schaible <jo...@gmx.de>.
+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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
[RESULT][all] Switch to Jira
Posted by Henri Yandell <fl...@gmail.com>.
14 +1s
1 +0.5s
So the move to Jira is on.
I did a practice one the other day and things seemed to work. I even
did some Jelly scripting to automate some parts of the migration.
Hen
On 5/2/06, Henri Yandell <fl...@gmail.com> 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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Davanum Srinivas <da...@gmail.com>.
+1
On 5/2/06, Oleg Kalnichevski <ol...@apache.org> 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 "XXXX".
> > ** 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: commons-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: commons-dev-help@jakarta.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
Re: [VOTE][all] Switch to Jira
Posted by Oleg Kalnichevski <ol...@apache.org>.
+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 "XXXX".
> ** 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: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
RE: [VOTE][all] Switch to Jira
Posted by James Carman <ja...@carmanconsulting.com>.
+1
-----Original Message-----
From: Henri Yandell [mailto:flamefew@gmail.com]
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 "XXXX".
** 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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org