[Pharo-dev] Patches for Pharo packages you are maintaining

Esteban Lorenzano estebanlm at gmail.com
Sun Nov 24 04:23:41 EST 2013

he, no, we are not going to re-migrate anytime soon :)
last year we needed a solution and we find it with fogbugz. Now, probably
it does not fits completely with our process or our openness our other
stuff, but still we have a reality: changing it is a lot of effort and even
if fogbugz is not perfect, it works.
So... until we have time and a *proven* better solution, we will not change

As Stef said, the right step (now) is to make what we have work better, not
run away from it :)
And of course, I'm not saying not to change ever... just not doing it
impulsively and without reasoning...


On Sun, Nov 24, 2013 at 10:15 AM, phil at highoctane.be <phil at highoctane.be>wrote:

> For the easiest thing in town, I'd say "Atlassian Jira"
> https://www.atlassian.com/opensource/overview
> I am using Fogbugz and JIRA on several client projects and JIRA definitely
> has more traction and engagement.
> But, migrating may be less painful than before:
> https://confluence.atlassian.com/display/JIRA/Importing+Data+from+FogBugz+for+Your+Server
> https://www.atlassian.com/software/jira/importer-migrations#!jira-fogbugz
> Phil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.pharo.org/pipermail/pharo-dev_lists.pharo.org/attachments/20131124/a47a6eef/attachment-0002.html>

More information about the Pharo-dev mailing list