request Calypso added as a "project" in Fogbugz
Can Calypso be added as a "project" in Fogbugz? I went to create an issue but could not find an appropriate place to file it under. As a backup I add an issue to the github tracker... https://github.com/dionisiydk/Calypso/issues/235 However I have some concerns about scattering Issues away from Fogbugz since this makes it harder to get an overview of outstanding issues (particularly leading up to a Release), and also the github tracker doesn't have priorities. fyi, here is the report... In Pharo 60540, using Nautilus to view the Delay class definition, selecting class variable 'Scheduler' > right-click > Code search > references to it produces 13 results. In Pharo-7.0+alpha.build.762.sha.0e0fe47c5 doing the same with Calypso produces 0 results. It still works with Nautilus. cheers -ben
On 13 Apr 2018, at 11:28, Ben Coman <btc@openinworld.com> wrote:
Can Calypso be added as a "project" in Fogbugz? I went to create an issue but could not find an appropriate place to file it under.
I added it.
As a backup I add an issue to the github tracker... https://github.com/dionisiydk/Calypso/issues/235 <https://github.com/dionisiydk/Calypso/issues/235>
However I have some concerns about scattering Issues away from Fogbugz since this makes it harder to get an overview of outstanding issues (particularly leading up to a Release), and also the github tracker doesn't have priorities.
fyi, here is the report... In Pharo 60540, using Nautilus to view the Delay class definition, selecting class variable 'Scheduler' > right-click > Code search > references to it produces 13 results.
In Pharo-7.0+alpha.build.762.sha.0e0fe47c5 doing the same with Calypso produces 0 results. It still works with Nautilus.
cheers -ben
Ben Coman wrote
However I have some concerns about scattering Issues away from Fogbugz since this makes it harder to get an overview of outstanding issues
Point taken, but: - IIUC we will be soon moving to *all* github issues anyway - duplication has it's own negative consequences - There are significant benefits to GH issues for GH code like all the auto-references (issues, commits, etc) ----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
On 13 April 2018 at 21:24, Sean P. DeNigris <sean@clipperadams.com> wrote:
Ben Coman wrote
However I have some concerns about scattering Issues away from Fogbugz since this makes it harder to get an overview of outstanding issues
Point taken, but: - IIUC we will be soon moving to *all* github issues anyway - duplication has it's own negative consequences - There are significant benefits to GH issues for GH code like all the auto-references (issues, commits, etc)
What is lacking from the Git/Fogbugz integration? Is it just that it hasn't been used/promoted much? (Is it enabled?) cheers -ben
Ben Coman wrote
What is lacking from the Git/Fogbugz integration?
I didn't even know about that! Although from a purely practical standpoint, I suspect we lose *a lot* of reports that never get made when the first hurdle is to create an account on Fogbugz vs. GH which practically every dev is on already⦠----- Cheers, Sean -- Sent from: http://forum.world.st/Pharo-Smalltalk-Developers-f1294837.html
participants (3)
-
Ben Coman -
Marcus Denker -
Sean P. DeNigris