Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-29 Thread Tobias Oetiker
Hi Ivan, thanks for your suggestions ... Apr 11 Ivan Pogorelov wrote: > Hi, > > I checked und found that: > > *Bugzilla Field**IsserTracker**Import Result* > Subject Titleok > Severity ???data loss added as tags > Priori

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-28 Thread Tobi Oetiker
Benoit It now looks like we will be able to add the bugs to the qooxdoo repo itself. So you will be able to add extra comments to bugs there. I will spend some time tomorrow trying to follow up on the issues raised regarding the migration script to bring this into a usable state. cheers tobi

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-28 Thread benco
Hi guys, Just a question regarding this great effort - thanks for making this possible ;) ... In practice how should we process to re-open these bugs ? Is there any process that will transfer reopened bugs to the official github repository ? Or should we ... copy-paste the content ? Regards, Be

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-11 Thread Ivan Pogorelov
Hi, I checked und found that: *Bugzilla Field**IsserTracker**Import Result* Subject Titleok Severity ???data loss Priority??? data loss Platform ??? data los

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-09 Thread Phyo Arkar
WOW , That is coool! Thanks community for keeping this up! You guys rock!! On Fri, Apr 8, 2016 at 8:56 PM, Derrell Lipman < derrell.lip...@unwireduniverse.com> wrote: > > On Fri, Apr 8, 2016 at 10:22 AM Tobias Oetiker wrote: > >> Today Derrell Lipman wrote: >> >> > On Fri, Apr 8, 2016 at 7:32 AM

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Derrell Lipman
On Fri, Apr 8, 2016 at 10:22 AM Tobias Oetiker wrote: > Today Derrell Lipman wrote: > > > On Fri, Apr 8, 2016 at 7:32 AM Tobias Oetiker wrote: > > > > > for now the bug migrator just closes all the imported bugs ... > > > > > > my idea in connection with this is, that in this way we have > > > t

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Tobias Oetiker
Today Derrell Lipman wrote: > On Fri, Apr 8, 2016 at 7:32 AM Tobias Oetiker wrote: > > > for now the bug migrator just closes all the imported bugs ... > > > > my idea in connection with this is, that in this way we have > > the option to 're-open' an issue that is still relevant, but then > > it

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Dietrich Streifert
Am 08.04.2016 um 13:32 schrieb Tobias Oetiker: > for now the bug migrator just closes all the imported bugs ... > > my idea in connection with this is, that in this way we have > the option to 're-open' an issue that is still relevant, but then > it is clear WHO re-opened it ... otherwhise we will

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Derrell Lipman
On Fri, Apr 8, 2016 at 7:32 AM Tobias Oetiker wrote: > for now the bug migrator just closes all the imported bugs ... > > my idea in connection with this is, that in this way we have > the option to 're-open' an issue that is still relevant, but then > it is clear WHO re-opened it ... otherwhise

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Fritz Zaucker
We could then have a bug-reopening party ... ;-) On Fri, 8 Apr 2016, Tobias Oetiker wrote: > Hi Derrell > > Today Derrell Lipman wrote: > >> I, too, would prefer to see them all in one place, in the qooxdoo issue >> tracker. (Then, we should have a dead bug clean-up party and close all of >> the

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread John Spackman
+1 - the integration provided by github issues is so much better than bugzilla, having the archive on there too is great, IMHO it’s a no brainer to ditch BZ altogether now On 08/04/2016, 11:24, "qooxdoo Development on behalf of Dietrich Streifert" wrote: >Hi Tobi, > >I'd advocate for imp

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Tobias Oetiker
Hi Derrell Today Derrell Lipman wrote: > I, too, would prefer to see them all in one place, in the qooxdoo issue > tracker. (Then, we should have a dead bug clean-up party and close all of > the ones that are no longer relevant or that we don't expect to ever > tackle.) for now the bug migrator

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Derrell Lipman
I, too, would prefer to see them all in one place, in the qooxdoo issue tracker. (Then, we should have a dead bug clean-up party and close all of the ones that are no longer relevant or that we don't expect to ever tackle.) Derrell On Fri, Apr 8, 2016 at 6:24 AM Dietrich Streifert < dietrich.str

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Dietrich Streifert
Hi Tobi, I'd advocate for importing the bugs into qooxdoo issue tracker. Regards Dietrich Am 08.04.2016 um 11:45 schrieb Tobias Oetiker: > Qooxdooers > > I have written a qooxdoo bugzilla to github migration software > which generated > > https://github.com/qx-bug-importer/qooxdoo-old-bugs/issue

Re: [qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Tobias Oetiker
Today Tobias Oetiker wrote: > Qooxdooers > > I have written a qooxdoo bugzilla to github migration software > which generated > > https://github.com/qx-bug-importer/qooxdoo-old-bugs/issues?utf8=%E2%9C%93&q= > > I have copied all 9252 bugs from bugzilla ... > > Using an experimental API I am now ab

[qooxdoo-devel] the bugzilla migration ...

2016-04-08 Thread Tobias Oetiker
Qooxdooers I have written a qooxdoo bugzilla to github migration software which generated https://github.com/qx-bug-importer/qooxdoo-old-bugs/issues?utf8=%E2%9C%93&q= I have copied all 9252 bugs from bugzilla ... Using an experimental API I am now able to migrate the bugs without causing notifi