[Pharo-dev] Patches for Pharo packages you are maintaining
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"
> 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:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pharo-dev