migration of bugs to the new platform

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

migration of bugs to the new platform

Francisco Puga
hi all,

I open a new thread. The old one about this has the name  "Any news
about gvSIG maven repository?"

I work a bit on this. See the attachment (spanish) for the workflow
i'm following. Only some comments:

* Attachments are lost
* The importer plugin does not handle the import of comments but i
think that after the issues have been upload it can be done.
* I almost have the csv files needed for use the importer but there
are some issues:

1.- The "author" can be taken from the csv or use nick of the person
that makes the import. But, if they are taken from the csv, only the
bugs that have an author that exists in the redmine are imported.
Maybe we can hack the plugin to use the importer id in the case that
the author id does not exist but the plugin it's written in ruby...
Anyone can take a look?
2.- Something similar happens with de "asignee"
3.- The new bugs are going to have a different id that the old ones.
Maybe some redmine expert can fix this, but i can't. My idea is create
a new custom field, that will be filled with the old id.
4.- I think that some of the old custom fields, does not exists in the
new installation. Or some projects are now split... someone that know
how the old and the new installation was set should take a look at
this.

I attach also a dump in sql and csv of the table.

Tomorrow i will be in the IRC since 12'00 (maybe before). It would be
nice in some of the admin can be there to discuss this. Also we can
make a skype or an phone call when you want.

cheers.


---------- Mensaje reenviado ----------
De: Francisco Puga <[hidden email]>
Fecha: 10 de enero de 2012 12:54
Asunto: Re: [gvSIG-TSC] Any news about gvSIG maven repository?
Para: Public mailing list for the Technical Steering Committee of the
gvSIG Project <[hidden email]>


Hi all,

I get this two files as an sql dump of the gvSIG tracker. I think that
the attaches are not included, but it seems good. I didn't review it
so much. I'm going to take a look at the importer and see how the
import can be done.

http://dl.dropbox.com/u/2131623/mig_comments_gvsig.sql.gz
http://dl.dropbox.com/u/2131623/mig_issues_gvsig.sql.gz


El día 30 de diciembre de 2011 17:21, Cèsar Ordiñana
<[hidden email]> escribió:

> El 30/12/11 12:09, Francisco Puga escribió:
>
>> Hi all,
>>
>> I write yesterday to join-up maintainers asking if there is a way to
>> get a dump of the tracker of the project i admin. I told then, that i
>> was also involved in the gvSIG project and it will be nice if we get a
>> dump of this project to.
>>
>> As i think that they already have a script to pull the bugs from
>> gforge (the migrate it to join-up), i suggest him to dump the bugs in
>> something like a json format. I offer myself to help them in this.
>>
>> Having the bugs in a json format i think that will not be so difficult
>> build a "pusher" to the redmine. Migrate the bugs, the comments, the
>> patches, etc ... by hand seems impossible to me.
>
>
> Thanks Francisco, that would be fantastic if we could have some way to
> import all the osor trackers into the new ones.
>
> I have no idea how much it will cost to perform the "push" into redmine. The
> problem is that we are very low on resources to prepare that process, but
> maybe we could use something like the redmine importer plugin [1]. It
> requires to import from a CSV file, and I don't know if it supports comments
> and attachments, but its better than nothing.
>
> In any case, please keep us informed if the join-up maintainers agree on
> handing us any type of export. If at least we had the export already solved
> by the join-up people, so much the better.
>
> [1] http://www.redmine.org/plugins/importer
>
>
> Regards,
>
> --
> Cèsar Ordiñana Navarro
> gvSIG software architect
> DiSiD Technologies (http://www.disid.com)
>
>


--
Francisco Puga
Grupo de Desarrollo
Cartolab - Laboratorio de Ingeniería Cartográfica.
http://www.cartolab.es

ETS Ingeniería de Caminos, Canales y Puertos
Universidade da Coruña
Campus de Elviña - 15071 A Coruña (España)
(34)981167000 ext. 5493


--
Francisco Puga
Grupo de Desarrollo
Cartolab - Laboratorio de Ingeniería Cartográfica.
http://www.cartolab.es

ETS Ingeniería de Caminos, Canales y Puertos
Universidade da Coruña
Campus de Elviña - 15071 A Coruña (España)
(34)981167000 ext. 5493

Redmine.txt (9K) Download Attachment
desktop_issues.tgz (2M) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration of bugs to the new platform

Cèsar Ordiñana-3
El 10/01/12 20:40, Francisco Puga escribió:

> hi all,
>
> I open a new thread. The old one about this has the name  "Any news
> about gvSIG maven repository?"
>
> I work a bit on this. See the attachment (spanish) for the workflow
> i'm following. Only some comments:
>
> * Attachments are lost
> * The importer plugin does not handle the import of comments but i
> think that after the issues have been upload it can be done.
> * I almost have the csv files needed for use the importer but there
> are some issues:

Great work! Kudos to you Francisco!!!

> 1.- The "author" can be taken from the csv or use nick of the person
> that makes the import. But, if they are taken from the csv, only the
> bugs that have an author that exists in the redmine are imported.
> Maybe we can hack the plugin to use the importer id in the case that
> the author id does not exist but the plugin it's written in ruby...
> Anyone can take a look?

Another option would be to change the generated CSV file, by replacing
non existing users with another user, maybe one created for the import
so it becames clear those issues where imported from OSOR. In the
previous migration to the old Trac issues repository to OSOR something
similar was done.

> 2.- Something similar happens with de "asignee"

In that case I think it might be ignored. Closed issues don't need that,
and open ones I think would be interesting to be reviewed and reassigned
anyway.

> 3.- The new bugs are going to have a different id that the old ones.
> Maybe some redmine expert can fix this, but i can't. My idea is create
> a new custom field, that will be filled with the old id.

I think also the new custom field is the way to go. We are going to lose
the automatic links between issues and changesets, but it will happen
anyway as the redmine format is not the same as the gforge one
(changesets use the format rREVISION and issues use the format
#ISSUENUMBER without any prefix).

> 4.- I think that some of the old custom fields, does not exists in the
> new installation. Or some projects are now split... someone that know
> how the old and the new installation was set should take a look at
> this.

Yes, some of the fields have been changed or not included, following the
evolution of the way the project works. I think those old custom fields,
although its a pity to lose some information, might be safely ignored.

> I attach also a dump in sql and csv of the table.
> Tomorrow i will be in the IRC since 12'00 (maybe before). It would be
> nice in some of the admin can be there to discuss this. Also we can
> make a skype or an phone call when you want.

I think I will be in the IRC tomorrow too.

Thanks again!

> cheers.
>
>
> ---------- Mensaje reenviado ----------
> De: Francisco Puga<[hidden email]>
> Fecha: 10 de enero de 2012 12:54
> Asunto: Re: [gvSIG-TSC] Any news about gvSIG maven repository?
> Para: Public mailing list for the Technical Steering Committee of the
> gvSIG Project<[hidden email]>
>
>
> Hi all,
>
> I get this two files as an sql dump of the gvSIG tracker. I think that
> the attaches are not included, but it seems good. I didn't review it
> so much. I'm going to take a look at the importer and see how the
> import can be done.
>
> http://dl.dropbox.com/u/2131623/mig_comments_gvsig.sql.gz
> http://dl.dropbox.com/u/2131623/mig_issues_gvsig.sql.gz
>
>
> El día 30 de diciembre de 2011 17:21, Cèsar Ordiñana
> <[hidden email]>  escribió:
>> El 30/12/11 12:09, Francisco Puga escribió:
>>
>>> Hi all,
>>>
>>> I write yesterday to join-up maintainers asking if there is a way to
>>> get a dump of the tracker of the project i admin. I told then, that i
>>> was also involved in the gvSIG project and it will be nice if we get a
>>> dump of this project to.
>>>
>>> As i think that they already have a script to pull the bugs from
>>> gforge (the migrate it to join-up), i suggest him to dump the bugs in
>>> something like a json format. I offer myself to help them in this.
>>>
>>> Having the bugs in a json format i think that will not be so difficult
>>> build a "pusher" to the redmine. Migrate the bugs, the comments, the
>>> patches, etc ... by hand seems impossible to me.
>>
>> Thanks Francisco, that would be fantastic if we could have some way to
>> import all the osor trackers into the new ones.
>>
>> I have no idea how much it will cost to perform the "push" into redmine. The
>> problem is that we are very low on resources to prepare that process, but
>> maybe we could use something like the redmine importer plugin [1]. It
>> requires to import from a CSV file, and I don't know if it supports comments
>> and attachments, but its better than nothing.
>>
>> In any case, please keep us informed if the join-up maintainers agree on
>> handing us any type of export. If at least we had the export already solved
>> by the join-up people, so much the better.
>>
>> [1] http://www.redmine.org/plugins/importer
>>
>>
>> Regards,
>>
>> --
>> Cèsar Ordiñana Navarro
>> gvSIG software architect
>> DiSiD Technologies (http://www.disid.com)
>>
>>
>
>
> --
> Francisco Puga
> Grupo de Desarrollo
> Cartolab - Laboratorio de Ingeniería Cartográfica.
> http://www.cartolab.es
>
> ETS Ingeniería de Caminos, Canales y Puertos
> Universidade da Coruña
> Campus de Elviña - 15071 A Coruña (España)
> (34)981167000 ext. 5493
>
>


--
Cèsar Ordiñana Navarro
gvSIG software architect
DiSiD Technologies (http://www.disid.com)


Reply | Threaded
Open this post in threaded view
|

Re: migration of bugs to the new platform

Francisco Puga
Hi,

I'm going to write spanish, if some non-spanish reader are following
the thread, don't hesitate, tell us, and i will rewrite the mail.

Hoy pude volver a ponerme con esto y se puede decir que ya lo tengo
listo, pero sería MUY importante que los project admin leyeran el
documento adjunto Redmind.txt para que vieran el proceso y comentaran
cualquier cosa que chirrie.

La api rest de redmine no permite crear comentarios por lo que opté,
por meter los comentarios dentro de la propia descripción del ticket.

Hay algunas cosas que quedarían por hacer para completar la migración.

Por parte de los administradores:
- Instalar el plugin de importación desde csv
- Crear los valores que faltan en los custom fields. Para que la
importación funcione los valores que se le pasan a los custom fields
tienen que existir previamente (o estar en blanco). Por ejemplo hay
bugs que tienen versión "1.1.2" pero esa versión no está metida en el
tracker. En el adjunto vienen todos los valores que he empleado en los
distintos custom fields.
- Crear un nuevo usuario osor_migration o lo que se quiera para meter
los bugs creados por usuarios que no existen en el redmine actual
- Pasarme una lista de los nicks de la gente metida actualmente en el
redmine. En el volcado de osor están los correos-e pero el importador
necesita que el valor de ese campo sea igual al nick empleado en el
tracker
- Decidir que hacer con el tampo Categoría, que se correspondería
ahora con el campo "Tipo" o "Tracker". Más información en el adjunto.
- Crear un nuevo custo field del tipo old_osor_id
- Decidir si emparejamos el campo Categoría con los antiguos de osor o pasamos

Por mi parte:
- Una vez me respondais a las cosas de arriba hacer los cambios y
pasaros de nuevo el fichero

migracion.tgz es un csv con como están ahora las cosas por si queréis
hacer una prueba. En caso de que por mail sea dificil de discutir lo
que queda por hacer podéis llamarme al tlf del laboratorio.


Igual se me olvida algo, pero lo vamos viendo :)

El día 11 de enero de 2012 11:51, Cèsar Ordiñana
<[hidden email]> escribió:

> El 10/01/12 20:40, Francisco Puga escribió:
>
>> hi all,
>>
>> I open a new thread. The old one about this has the name  "Any news
>> about gvSIG maven repository?"
>>
>> I work a bit on this. See the attachment (spanish) for the workflow
>> i'm following. Only some comments:
>>
>> * Attachments are lost
>> * The importer plugin does not handle the import of comments but i
>> think that after the issues have been upload it can be done.
>> * I almost have the csv files needed for use the importer but there
>> are some issues:
>
>
> Great work! Kudos to you Francisco!!!
>
>
>> 1.- The "author" can be taken from the csv or use nick of the person
>> that makes the import. But, if they are taken from the csv, only the
>> bugs that have an author that exists in the redmine are imported.
>> Maybe we can hack the plugin to use the importer id in the case that
>> the author id does not exist but the plugin it's written in ruby...
>> Anyone can take a look?
>
>
> Another option would be to change the generated CSV file, by replacing non
> existing users with another user, maybe one created for the import so it
> becames clear those issues where imported from OSOR. In the previous
> migration to the old Trac issues repository to OSOR something similar was
> done.
>
>
>> 2.- Something similar happens with de "asignee"
>
>
> In that case I think it might be ignored. Closed issues don't need that, and
> open ones I think would be interesting to be reviewed and reassigned anyway.
>
>
>> 3.- The new bugs are going to have a different id that the old ones.
>> Maybe some redmine expert can fix this, but i can't. My idea is create
>> a new custom field, that will be filled with the old id.
>
>
> I think also the new custom field is the way to go. We are going to lose the
> automatic links between issues and changesets, but it will happen anyway as
> the redmine format is not the same as the gforge one (changesets use the
> format rREVISION and issues use the format #ISSUENUMBER without any prefix).
>
>
>> 4.- I think that some of the old custom fields, does not exists in the
>> new installation. Or some projects are now split... someone that know
>> how the old and the new installation was set should take a look at
>> this.
>
>
> Yes, some of the fields have been changed or not included, following the
> evolution of the way the project works. I think those old custom fields,
> although its a pity to lose some information, might be safely ignored.
>
>
>> I attach also a dump in sql and csv of the table.
>> Tomorrow i will be in the IRC since 12'00 (maybe before). It would be
>> nice in some of the admin can be there to discuss this. Also we can
>> make a skype or an phone call when you want.
>
>
> I think I will be in the IRC tomorrow too.
>
> Thanks again!
>
>
>> cheers.
>>
>>
>> ---------- Mensaje reenviado ----------
>> De: Francisco Puga<[hidden email]>
>> Fecha: 10 de enero de 2012 12:54
>> Asunto: Re: [gvSIG-TSC] Any news about gvSIG maven repository?
>> Para: Public mailing list for the Technical Steering Committee of the
>> gvSIG Project<[hidden email]>
>>
>>
>> Hi all,
>>
>> I get this two files as an sql dump of the gvSIG tracker. I think that
>> the attaches are not included, but it seems good. I didn't review it
>> so much. I'm going to take a look at the importer and see how the
>> import can be done.
>>
>> http://dl.dropbox.com/u/2131623/mig_comments_gvsig.sql.gz
>> http://dl.dropbox.com/u/2131623/mig_issues_gvsig.sql.gz
>>
>>
>> El día 30 de diciembre de 2011 17:21, Cèsar Ordiñana
>> <[hidden email]>  escribió:
>>>
>>> El 30/12/11 12:09, Francisco Puga escribió:
>>>
>>>> Hi all,
>>>>
>>>> I write yesterday to join-up maintainers asking if there is a way to
>>>> get a dump of the tracker of the project i admin. I told then, that i
>>>> was also involved in the gvSIG project and it will be nice if we get a
>>>> dump of this project to.
>>>>
>>>> As i think that they already have a script to pull the bugs from
>>>> gforge (the migrate it to join-up), i suggest him to dump the bugs in
>>>> something like a json format. I offer myself to help them in this.
>>>>
>>>> Having the bugs in a json format i think that will not be so difficult
>>>> build a "pusher" to the redmine. Migrate the bugs, the comments, the
>>>> patches, etc ... by hand seems impossible to me.
>>>
>>>
>>> Thanks Francisco, that would be fantastic if we could have some way to
>>> import all the osor trackers into the new ones.
>>>
>>> I have no idea how much it will cost to perform the "push" into redmine.
>>> The
>>> problem is that we are very low on resources to prepare that process, but
>>> maybe we could use something like the redmine importer plugin [1]. It
>>> requires to import from a CSV file, and I don't know if it supports
>>> comments
>>> and attachments, but its better than nothing.
>>>
>>> In any case, please keep us informed if the join-up maintainers agree on
>>> handing us any type of export. If at least we had the export already
>>> solved
>>> by the join-up people, so much the better.
>>>
>>> [1] http://www.redmine.org/plugins/importer
>>>
>>>
>>> Regards,
>>>
>>> --
>>> Cèsar Ordiñana Navarro
>>> gvSIG software architect
>>> DiSiD Technologies (http://www.disid.com)
>>>
>>>
>>
>>
>> --
>> Francisco Puga
>> Grupo de Desarrollo
>> Cartolab - Laboratorio de Ingeniería Cartográfica.
>> http://www.cartolab.es
>>
>> ETS Ingeniería de Caminos, Canales y Puertos
>> Universidade da Coruña
>> Campus de Elviña - 15071 A Coruña (España)
>> (34)981167000 ext. 5493
>>
>>
>
>
> --
> Cèsar Ordiñana Navarro
> gvSIG software architect
> DiSiD Technologies (http://www.disid.com)
>
>


--
Francisco Puga
Grupo de Desarrollo
Cartolab - Laboratorio de Ingeniería Cartográfica.
http://www.cartolab.es

ETS Ingeniería de Caminos, Canales y Puertos
Universidade da Coruña
Campus de Elviña - 15071 A Coruña (España)
(34)981167000 ext. 5493

Redmine.txt (27K) Download Attachment
migracion.tgz (1M) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: migration of bugs to the new platform

Jorge Sanz (Prodevelop)
El 16/01/12 19:56, Francisco Puga escribió:

> Hi,
>
> I'm going to write spanish, if some non-spanish reader are following
> the thread, don't hesitate, tell us, and i will rewrite the mail.
>
> Hoy pude volver a ponerme con esto y se puede decir que ya lo tengo
> listo, pero sería MUY importante que los project admin leyeran el
> documento adjunto Redmind.txt para que vieran el proceso y comentaran
> cualquier cosa que chirrie.
>
> La api rest de redmine no permite crear comentarios por lo que opté,
> por meter los comentarios dentro de la propia descripción del ticket.
>
> Hay algunas cosas que quedarían por hacer para completar la migración.
>
> Por parte de los administradores:
> - Instalar el plugin de importación desde csv
> - Crear los valores que faltan en los custom fields. Para que la
> importación funcione los valores que se le pasan a los custom fields
> tienen que existir previamente (o estar en blanco). Por ejemplo hay
> bugs que tienen versión "1.1.2" pero esa versión no está metida en el
> tracker. En el adjunto vienen todos los valores que he empleado en los
> distintos custom fields.
> - Crear un nuevo usuario osor_migration o lo que se quiera para meter
> los bugs creados por usuarios que no existen en el redmine actual
> - Pasarme una lista de los nicks de la gente metida actualmente en el
> redmine. En el volcado de osor están los correos-e pero el importador
> necesita que el valor de ese campo sea igual al nick empleado en el
> tracker
> - Decidir que hacer con el tampo Categoría, que se correspondería
> ahora con el campo "Tipo" o "Tracker". Más información en el adjunto.
> - Crear un nuevo custo field del tipo old_osor_id
> - Decidir si emparejamos el campo Categoría con los antiguos de osor o pasamos
>
> Por mi parte:
> - Una vez me respondais a las cosas de arriba hacer los cambios y
> pasaros de nuevo el fichero
>
> migracion.tgz es un csv con como están ahora las cosas por si queréis
> hacer una prueba. En caso de que por mail sea dificil de discutir lo
> que queda por hacer podéis llamarme al tlf del laboratorio.
>
>
> Igual se me olvida algo, pero lo vamos viendo :)

Wow Fran eso suena muy bien, muchas gracias de verdad por el curro!!

--
Jorge Gaspar Sanz Salinas
http://www.prodevelop.es
tfno: +34 963 510 612



Reply | Threaded
Open this post in threaded view
|

Re: migration of bugs to the new platform

Pablo Sanxiao-3
In reply to this post by Francisco Puga
Hola,

alguna de las personas que administra el redmine ha podido echarle un
ojo a las cosas que comentaba Fran Puga?

Necesitaríamos que se completase esta migración para poder empezar a
trabajar sobre el redmine en la 1.12 lo antes posible. A parte de que
sería una pena que se perdiese el tremendo trabajo que se ha hecho para
automatizar lo máximo posible la migración.

Saludos,
Pablo


On 16/01/12 19:56, Francisco Puga wrote:

> Hi,
>
> I'm going to write spanish, if some non-spanish reader are following
> the thread, don't hesitate, tell us, and i will rewrite the mail.
>
> Hoy pude volver a ponerme con esto y se puede decir que ya lo tengo
> listo, pero sería MUY importante que los project admin leyeran el
> documento adjunto Redmind.txt para que vieran el proceso y comentaran
> cualquier cosa que chirrie.
>
> La api rest de redmine no permite crear comentarios por lo que opté,
> por meter los comentarios dentro de la propia descripción del ticket.
>
> Hay algunas cosas que quedarían por hacer para completar la migración.
>
> Por parte de los administradores:
> - Instalar el plugin de importación desde csv
> - Crear los valores que faltan en los custom fields. Para que la
> importación funcione los valores que se le pasan a los custom fields
> tienen que existir previamente (o estar en blanco). Por ejemplo hay
> bugs que tienen versión "1.1.2" pero esa versión no está metida en el
> tracker. En el adjunto vienen todos los valores que he empleado en los
> distintos custom fields.
> - Crear un nuevo usuario osor_migration o lo que se quiera para meter
> los bugs creados por usuarios que no existen en el redmine actual
> - Pasarme una lista de los nicks de la gente metida actualmente en el
> redmine. En el volcado de osor están los correos-e pero el importador
> necesita que el valor de ese campo sea igual al nick empleado en el
> tracker
> - Decidir que hacer con el tampo Categoría, que se correspondería
> ahora con el campo "Tipo" o "Tracker". Más información en el adjunto.
> - Crear un nuevo custo field del tipo old_osor_id
> - Decidir si emparejamos el campo Categoría con los antiguos de osor o pasamos
>
> Por mi parte:
> - Una vez me respondais a las cosas de arriba hacer los cambios y
> pasaros de nuevo el fichero
>
> migracion.tgz es un csv con como están ahora las cosas por si queréis
> hacer una prueba. En caso de que por mail sea dificil de discutir lo
> que queda por hacer podéis llamarme al tlf del laboratorio.
>
>
> Igual se me olvida algo, pero lo vamos viendo :)
>
> El día 11 de enero de 2012 11:51, Cèsar Ordiñana
> <[hidden email]>  escribió:
>> El 10/01/12 20:40, Francisco Puga escribió:
>>
>>> hi all,
>>>
>>> I open a new thread. The old one about this has the name  "Any news
>>> about gvSIG maven repository?"
>>>
>>> I work a bit on this. See the attachment (spanish) for the workflow
>>> i'm following. Only some comments:
>>>
>>> * Attachments are lost
>>> * The importer plugin does not handle the import of comments but i
>>> think that after the issues have been upload it can be done.
>>> * I almost have the csv files needed for use the importer but there
>>> are some issues:
>>
>> Great work! Kudos to you Francisco!!!
>>
>>
>>> 1.- The "author" can be taken from the csv or use nick of the person
>>> that makes the import. But, if they are taken from the csv, only the
>>> bugs that have an author that exists in the redmine are imported.
>>> Maybe we can hack the plugin to use the importer id in the case that
>>> the author id does not exist but the plugin it's written in ruby...
>>> Anyone can take a look?
>>
>> Another option would be to change the generated CSV file, by replacing non
>> existing users with another user, maybe one created for the import so it
>> becames clear those issues where imported from OSOR. In the previous
>> migration to the old Trac issues repository to OSOR something similar was
>> done.
>>
>>
>>> 2.- Something similar happens with de "asignee"
>>
>> In that case I think it might be ignored. Closed issues don't need that, and
>> open ones I think would be interesting to be reviewed and reassigned anyway.
>>
>>
>>> 3.- The new bugs are going to have a different id that the old ones.
>>> Maybe some redmine expert can fix this, but i can't. My idea is create
>>> a new custom field, that will be filled with the old id.
>>
>> I think also the new custom field is the way to go. We are going to lose the
>> automatic links between issues and changesets, but it will happen anyway as
>> the redmine format is not the same as the gforge one (changesets use the
>> format rREVISION and issues use the format #ISSUENUMBER without any prefix).
>>
>>
>>> 4.- I think that some of the old custom fields, does not exists in the
>>> new installation. Or some projects are now split... someone that know
>>> how the old and the new installation was set should take a look at
>>> this.
>>
>> Yes, some of the fields have been changed or not included, following the
>> evolution of the way the project works. I think those old custom fields,
>> although its a pity to lose some information, might be safely ignored.
>>
>>
>>> I attach also a dump in sql and csv of the table.
>>> Tomorrow i will be in the IRC since 12'00 (maybe before). It would be
>>> nice in some of the admin can be there to discuss this. Also we can
>>> make a skype or an phone call when you want.
>>
>> I think I will be in the IRC tomorrow too.
>>
>> Thanks again!
>>
>>
>>> cheers.
>>>
>>>
>>> ---------- Mensaje reenviado ----------
>>> De: Francisco Puga<[hidden email]>
>>> Fecha: 10 de enero de 2012 12:54
>>> Asunto: Re: [gvSIG-TSC] Any news about gvSIG maven repository?
>>> Para: Public mailing list for the Technical Steering Committee of the
>>> gvSIG Project<[hidden email]>
>>>
>>>
>>> Hi all,
>>>
>>> I get this two files as an sql dump of the gvSIG tracker. I think that
>>> the attaches are not included, but it seems good. I didn't review it
>>> so much. I'm going to take a look at the importer and see how the
>>> import can be done.
>>>
>>> http://dl.dropbox.com/u/2131623/mig_comments_gvsig.sql.gz
>>> http://dl.dropbox.com/u/2131623/mig_issues_gvsig.sql.gz
>>>
>>>
>>> El día 30 de diciembre de 2011 17:21, Cèsar Ordiñana
>>> <[hidden email]>    escribió:
>>>> El 30/12/11 12:09, Francisco Puga escribió:
>>>>
>>>>> Hi all,
>>>>>
>>>>> I write yesterday to join-up maintainers asking if there is a way to
>>>>> get a dump of the tracker of the project i admin. I told then, that i
>>>>> was also involved in the gvSIG project and it will be nice if we get a
>>>>> dump of this project to.
>>>>>
>>>>> As i think that they already have a script to pull the bugs from
>>>>> gforge (the migrate it to join-up), i suggest him to dump the bugs in
>>>>> something like a json format. I offer myself to help them in this.
>>>>>
>>>>> Having the bugs in a json format i think that will not be so difficult
>>>>> build a "pusher" to the redmine. Migrate the bugs, the comments, the
>>>>> patches, etc ... by hand seems impossible to me.
>>>>
>>>> Thanks Francisco, that would be fantastic if we could have some way to
>>>> import all the osor trackers into the new ones.
>>>>
>>>> I have no idea how much it will cost to perform the "push" into redmine.
>>>> The
>>>> problem is that we are very low on resources to prepare that process, but
>>>> maybe we could use something like the redmine importer plugin [1]. It
>>>> requires to import from a CSV file, and I don't know if it supports
>>>> comments
>>>> and attachments, but its better than nothing.
>>>>
>>>> In any case, please keep us informed if the join-up maintainers agree on
>>>> handing us any type of export. If at least we had the export already
>>>> solved
>>>> by the join-up people, so much the better.
>>>>
>>>> [1] http://www.redmine.org/plugins/importer
>>>>
>>>>
>>>> Regards,
>>>>
>>>> --
>>>> Cèsar Ordiñana Navarro
>>>> gvSIG software architect
>>>> DiSiD Technologies (http://www.disid.com)
>>>>
>>>>
>>>
>>> --
>>> Francisco Puga
>>> Grupo de Desarrollo
>>> Cartolab - Laboratorio de Ingeniería Cartográfica.
>>> http://www.cartolab.es
>>>
>>> ETS Ingeniería de Caminos, Canales y Puertos
>>> Universidade da Coruña
>>> Campus de Elviña - 15071 A Coruña (España)
>>> (34)981167000 ext. 5493
>>>
>>>
>>
>> --
>> Cèsar Ordiñana Navarro
>> gvSIG software architect
>> DiSiD Technologies (http://www.disid.com)
>>
>>
>
>


--
Pablo Sanxiao Roca
Coordinador Área de Desarrollo
iCarto | Innovación, Cooperación, Cartografía y Territorio S.L.
http://www.icarto.es/

c/ Rafael Alberti nº 13 – 1º D
15008 A Coruña
Galicia (Spain)
+34 881927808


_______________________________________________
gvSIG-desktop-TSC-pub mailing list
http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub
Reply | Threaded
Open this post in threaded view
|

Re: migration of bugs to the new platform

Manuel Madrid-3
Hola Pablo.

Disculpad que no hayamos contestado antes.

Por supuesto nuestra intención es aprovechar el gran trabajo que ha
hecho Fran lo que pasa es que andamos escasos de personal estos días. A
ver si esta semana podemos desbloquearlo.

Saludos,
Manuel.

El 23/01/12 13:55, Pablo Sanxiao escribió:

> Hola,
>
> alguna de las personas que administra el redmine ha podido echarle un
> ojo a las cosas que comentaba Fran Puga?
>
> Necesitaríamos que se completase esta migración para poder empezar a
> trabajar sobre el redmine en la 1.12 lo antes posible. A parte de que
> sería una pena que se perdiese el tremendo trabajo que se ha hecho para
> automatizar lo máximo posible la migración.
>
> Saludos,
> Pablo
>
>
> On 16/01/12 19:56, Francisco Puga wrote:
>> Hi,
>>
>> I'm going to write spanish, if some non-spanish reader are following
>> the thread, don't hesitate, tell us, and i will rewrite the mail.
>>
>> Hoy pude volver a ponerme con esto y se puede decir que ya lo tengo
>> listo, pero sería MUY importante que los project admin leyeran el
>> documento adjunto Redmind.txt para que vieran el proceso y comentaran
>> cualquier cosa que chirrie.
>>
>> La api rest de redmine no permite crear comentarios por lo que opté,
>> por meter los comentarios dentro de la propia descripción del ticket.
>>
>> Hay algunas cosas que quedarían por hacer para completar la migración.
>>
>> Por parte de los administradores:
>> - Instalar el plugin de importación desde csv
>> - Crear los valores que faltan en los custom fields. Para que la
>> importación funcione los valores que se le pasan a los custom fields
>> tienen que existir previamente (o estar en blanco). Por ejemplo hay
>> bugs que tienen versión "1.1.2" pero esa versión no está metida en el
>> tracker. En el adjunto vienen todos los valores que he empleado en los
>> distintos custom fields.
>> - Crear un nuevo usuario osor_migration o lo que se quiera para meter
>> los bugs creados por usuarios que no existen en el redmine actual
>> - Pasarme una lista de los nicks de la gente metida actualmente en el
>> redmine. En el volcado de osor están los correos-e pero el importador
>> necesita que el valor de ese campo sea igual al nick empleado en el
>> tracker
>> - Decidir que hacer con el tampo Categoría, que se correspondería
>> ahora con el campo "Tipo" o "Tracker". Más información en el adjunto.
>> - Crear un nuevo custo field del tipo old_osor_id
>> - Decidir si emparejamos el campo Categoría con los antiguos de osor o
>> pasamos
>>
>> Por mi parte:
>> - Una vez me respondais a las cosas de arriba hacer los cambios y
>> pasaros de nuevo el fichero
>>
>> migracion.tgz es un csv con como están ahora las cosas por si queréis
>> hacer una prueba. En caso de que por mail sea dificil de discutir lo
>> que queda por hacer podéis llamarme al tlf del laboratorio.
>>
>>
>> Igual se me olvida algo, pero lo vamos viendo :)
>>
>> El día 11 de enero de 2012 11:51, Cèsar Ordiñana
>> <[hidden email]>  escribió:
>>> El 10/01/12 20:40, Francisco Puga escribió:
>>>
>>>> hi all,
>>>>
>>>> I open a new thread. The old one about this has the name  "Any news
>>>> about gvSIG maven repository?"
>>>>
>>>> I work a bit on this. See the attachment (spanish) for the workflow
>>>> i'm following. Only some comments:
>>>>
>>>> * Attachments are lost
>>>> * The importer plugin does not handle the import of comments but i
>>>> think that after the issues have been upload it can be done.
>>>> * I almost have the csv files needed for use the importer but there
>>>> are some issues:
>>>
>>> Great work! Kudos to you Francisco!!!
>>>
>>>
>>>> 1.- The "author" can be taken from the csv or use nick of the person
>>>> that makes the import. But, if they are taken from the csv, only the
>>>> bugs that have an author that exists in the redmine are imported.
>>>> Maybe we can hack the plugin to use the importer id in the case that
>>>> the author id does not exist but the plugin it's written in ruby...
>>>> Anyone can take a look?
>>>
>>> Another option would be to change the generated CSV file, by
>>> replacing non
>>> existing users with another user, maybe one created for the import so it
>>> becames clear those issues where imported from OSOR. In the previous
>>> migration to the old Trac issues repository to OSOR something similar
>>> was
>>> done.
>>>
>>>
>>>> 2.- Something similar happens with de "asignee"
>>>
>>> In that case I think it might be ignored. Closed issues don't need
>>> that, and
>>> open ones I think would be interesting to be reviewed and reassigned
>>> anyway.
>>>
>>>
>>>> 3.- The new bugs are going to have a different id that the old ones.
>>>> Maybe some redmine expert can fix this, but i can't. My idea is create
>>>> a new custom field, that will be filled with the old id.
>>>
>>> I think also the new custom field is the way to go. We are going to
>>> lose the
>>> automatic links between issues and changesets, but it will happen
>>> anyway as
>>> the redmine format is not the same as the gforge one (changesets use the
>>> format rREVISION and issues use the format #ISSUENUMBER without any
>>> prefix).
>>>
>>>
>>>> 4.- I think that some of the old custom fields, does not exists in the
>>>> new installation. Or some projects are now split... someone that know
>>>> how the old and the new installation was set should take a look at
>>>> this.
>>>
>>> Yes, some of the fields have been changed or not included, following the
>>> evolution of the way the project works. I think those old custom fields,
>>> although its a pity to lose some information, might be safely ignored.
>>>
>>>
>>>> I attach also a dump in sql and csv of the table.
>>>> Tomorrow i will be in the IRC since 12'00 (maybe before). It would be
>>>> nice in some of the admin can be there to discuss this. Also we can
>>>> make a skype or an phone call when you want.
>>>
>>> I think I will be in the IRC tomorrow too.
>>>
>>> Thanks again!
>>>
>>>
>>>> cheers.
>>>>
>>>>
>>>> ---------- Mensaje reenviado ----------
>>>> De: Francisco Puga<[hidden email]>
>>>> Fecha: 10 de enero de 2012 12:54
>>>> Asunto: Re: [gvSIG-TSC] Any news about gvSIG maven repository?
>>>> Para: Public mailing list for the Technical Steering Committee of the
>>>> gvSIG Project<[hidden email]>
>>>>
>>>>
>>>> Hi all,
>>>>
>>>> I get this two files as an sql dump of the gvSIG tracker. I think that
>>>> the attaches are not included, but it seems good. I didn't review it
>>>> so much. I'm going to take a look at the importer and see how the
>>>> import can be done.
>>>>
>>>> http://dl.dropbox.com/u/2131623/mig_comments_gvsig.sql.gz
>>>> http://dl.dropbox.com/u/2131623/mig_issues_gvsig.sql.gz
>>>>
>>>>
>>>> El día 30 de diciembre de 2011 17:21, Cèsar Ordiñana
>>>> <[hidden email]>    escribió:
>>>>> El 30/12/11 12:09, Francisco Puga escribió:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I write yesterday to join-up maintainers asking if there is a way to
>>>>>> get a dump of the tracker of the project i admin. I told then, that i
>>>>>> was also involved in the gvSIG project and it will be nice if we
>>>>>> get a
>>>>>> dump of this project to.
>>>>>>
>>>>>> As i think that they already have a script to pull the bugs from
>>>>>> gforge (the migrate it to join-up), i suggest him to dump the bugs in
>>>>>> something like a json format. I offer myself to help them in this.
>>>>>>
>>>>>> Having the bugs in a json format i think that will not be so
>>>>>> difficult
>>>>>> build a "pusher" to the redmine. Migrate the bugs, the comments, the
>>>>>> patches, etc ... by hand seems impossible to me.
>>>>>
>>>>> Thanks Francisco, that would be fantastic if we could have some way to
>>>>> import all the osor trackers into the new ones.
>>>>>
>>>>> I have no idea how much it will cost to perform the "push" into
>>>>> redmine.
>>>>> The
>>>>> problem is that we are very low on resources to prepare that
>>>>> process, but
>>>>> maybe we could use something like the redmine importer plugin [1]. It
>>>>> requires to import from a CSV file, and I don't know if it supports
>>>>> comments
>>>>> and attachments, but its better than nothing.
>>>>>
>>>>> In any case, please keep us informed if the join-up maintainers
>>>>> agree on
>>>>> handing us any type of export. If at least we had the export already
>>>>> solved
>>>>> by the join-up people, so much the better.
>>>>>
>>>>> [1] http://www.redmine.org/plugins/importer
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> --
>>>>> Cèsar Ordiñana Navarro
>>>>> gvSIG software architect
>>>>> DiSiD Technologies (http://www.disid.com)
>>>>>
>>>>>
>>>>
>>>> --
>>>> Francisco Puga
>>>> Grupo de Desarrollo
>>>> Cartolab - Laboratorio de Ingeniería Cartográfica.
>>>> http://www.cartolab.es
>>>>
>>>> ETS Ingeniería de Caminos, Canales y Puertos
>>>> Universidade da Coruña
>>>> Campus de Elviña - 15071 A Coruña (España)
>>>> (34)981167000 ext. 5493
>>>>
>>>>
>>>
>>> --
>>> Cèsar Ordiñana Navarro
>>> gvSIG software architect
>>> DiSiD Technologies (http://www.disid.com)
>>>
>>>
>>
>>
>
>

--
Manuel Madrid.
Product and testing manager.
gvSIG project (http://www.gvsig.org).

_______________________________________________
gvSIG-desktop-TSC-pub mailing list
http://joinup.ec.europa.eu/mailman/listinfo/gvsig-desktop-tsc-pub