Hi Peter,
Today Peter Schneider wrote:
> Hi there,
>
> are there any plans on migrating the _bugzilla_accounts_ as well?
> Or do I have to create (yet another) account?
since everything is going to github, you can just use your github
account. note though the migrated issues will all be owned
Hi there,
are there any plans on migrating the _bugzilla_accounts_ as well?
Or do I have to create (yet another) account?
/Peter
Am 3/21/2016 um 4:41 PM schrieb Tobias Oetiker:
> Qooxdooers!
>
> We are in the process of migrating qooxdoo resources to public
> infrastructure ... My current
This is one of the best thing happened to qooxdoo. Lets make Qooxdoo kick
Angular ass!
On Tue, Mar 22, 2016 at 4:24 PM John Spackman
wrote:
> +1 Good idea :)
>
> John
>
>
>
>
> On 21/03/2016, 15:54, "qooxdoo Development <
> qooxdoo-devel@lists.sourceforge.net> on
+1 Good idea :)
John
On 21/03/2016, 15:54, "qooxdoo Development
on behalf of Tobias Oetiker"
wrote:
>Qooxdooers!
>
>We are in the process of migrating qooxdoo resources to public
Today Derrell Lipman wrote:
> Essentially, this is making a backup of the bugzilla issues in the
> qooxdoo-bugzilla repository's issue tracker, but moving forward to keeping
> new issues in the qooxdoo repository's issue tracker. Am I interpreting
> that correctly?
yes
> If so, I propose that
Sounds reasonable. Thanks for the further explanation.
Derrell
On Mon, Mar 21, 2016 at 12:13 PM Tobias Oetiker wrote:
> Today Derrell Lipman wrote:
>
> > Essentially, this is making a backup of the bugzilla issues in the
> > qooxdoo-bugzilla repository's issue tracker, but
Essentially, this is making a backup of the bugzilla issues in the
qooxdoo-bugzilla repository's issue tracker, but moving forward to keeping
new issues in the qooxdoo repository's issue tracker. Am I interpreting
that correctly?
If so, I propose that the list of issues in qooxdoo-bugzilla be