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 the list of issues in qooxdoo-bugzilla be reviewed, > and, "relevant" issues moved into the qooxdoo issue tracker, so there's > only one place to look for the current issue list. (The meaning of > "relevant" should probably be discussed, however.) this can certainly be done, but someone has todo it ... AND everyone watching qooxdoo/qooxdoo will get notified for every issue and every comment migrated. my idea is that by having qooxdoo/qooxdoo-bugzilla, the people who are interested in fixing qooxdoo bugs can simply watch that repo too, and if someone re-opens an old bug there, they will get notified ... then the bug can be moved to the new repo and will thus get the benefit of all the goodness of by being in the same repo as the qooxdoo code. cheers tobi > Derrell > > > On Mon, Mar 21, 2016 at 11:41 AM Tobias Oetiker <t...@oetiker.ch> wrote: > > > Qooxdooers! > > > > We are in the process of migrating qooxdoo resources to public > > infrastructure ... My current focus is the issue tracker. > > > > The initial idea was to move all existing issues from > > bugzilla.qooxdoo.org to the qooxdoo repo on github. But it turnes > > out that the github issues api is not well suited to seamlessly > > migrate issues: > > > > * Issue numbers get assigned automatically and can not be > > imported > > > > * People who are 'watching' the repo get notified for every issue > > imported. > > > > * As soon as there are watchers, github applies severe > > ratelimiting to prevent notification storms. > > > > With all that in mind, I am going to implement the following: > > > > a) migrate (AND CLOSE) existing issues from bugzilla to > > github.com/qooxdoo/qooxdoo-bugzilla (within the week) > > > > b) enable the issues tab in > > github.com/qooxdoo/qooxdoo (already done) > > > > You can see what migrated issues will look like on > > > > https://github.com/oetiker/issuetest2/issues?q=is%3Aissue > > > > cheers > > tobi > > > > -- > > Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland > > www.oetiker.ch t...@oetiker.ch +41 62 775 9902 > > > > > > > > ------------------------------------------------------------------------------ > > Transform Data into Opportunity. > > Accelerate data analysis in your applications with > > Intel Data Analytics Acceleration Library. > > Click to learn more. > > http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 > > _______________________________________________ > > qooxdoo-devel mailing list > > qooxdoo-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > > -- Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland www.oetiker.ch t...@oetiker.ch +41 62 775 9902 ------------------------------------------------------------------------------ Transform Data into Opportunity. Accelerate data analysis in your applications with Intel Data Analytics Acceleration Library. Click to learn more. http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140 _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
