On dim. 31 déc. 2017 at 16:04, Andy Burnett <andy.burn...@knowinnovation.com> wrote:
> Denis wrote > >>> > > It's same as any other code. Just follow instructions > https://github.com/pharo-project/pharo/wiki/Contribute-a-fix-to-Pharo. It > is now simplified a lot. > > <<< > > Wow! That has improved a lot. I have bookmarked the site, and I now have a > reason to learn iceberg. > > Out of curiosity, and perhaps this has been answered elsewhere, why are we > using fogbugz for issue tracking, rather than github's issue tracker? I > know nothing much about either of them. I am just curious if fogbugz is > much better? > Hi, I think that one of the reason is that all the Pharo process is based on Fogbugz and migrating would takes month and add a lot of instability for few gain. > Cheers > Andy > -- Cyril Ferlicot https://ferlicot.fr http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France
